User interfaces for customized navigation routes

ABSTRACT

In some embodiments, an electronic device displays suggested routes based on the characteristics of respective vehicles. In some embodiments, an electronic device receives data for respective vehicles from a source external to the electronic device. In some embodiments, an electronic device anonymizes a vehicle identifier and determines customized suggested routes using the anonymized vehicle identifier.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 63/038,080, filed Jun. 11, 2020, and U.S. ProvisionalPatent Application No. 63/041,985, filed Jun. 21, 2020, the contents ofwhich are hereby incorporated by reference in their entireties for allpurposes.

FIELD OF THE DISCLOSURE

This disclosure relates generally to user interfaces that enable a userto view navigation routes that are customized for a respective vehicle.

BACKGROUND OF THE DISCLOSURE

User interaction with electronic devices has increased significantly inrecent years. These devices can be devices such as computers, tabletcomputers, televisions, multimedia devices, mobile devices, and thelike.

In some circumstances, an electronic device displays map userinterfaces. In some circumstances, map user interfaces display suggesteddirections and routes.

SUMMARY OF THE DISCLOSURE

Some embodiments described in this disclosure are directed to displayingsuggested routes based on the characteristics of respective vehicles.Some embodiments described in this disclosure are directed to receivingdata for respective vehicles from external sources. Some embodimentsdescribed in this disclosure are directed to anonymizing a vehicleidentifier.

The embodiments described in this disclosure provide the user with theability to view and select navigation routes that are customized for theuser's vehicles. This customization improves the user's overallexperience and interactions with the device. By customizing views androutes based on a user's vehicle, embodiments also decrease userinteraction time, which is particularly important where input devicesare battery-operated.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

The full descriptions of the embodiments are provided in the Drawingsand the Detailed Description, and it is understood that the Summaryprovided above does not limit the scope of the disclosure in any way.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Detailed Description below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6FF illustrate exemplary ways in which an electronic devicedisplays customized navigation routes in accordance with someembodiments of the disclosure.

FIG. 7 is a flow diagram illustrating a method of displaying customizednavigation routes in accordance with some embodiments of the disclosure.

FIGS. 8A-8CC illustrate exemplary ways in which an electronic devicereceives information about characteristics of respective vehicles inaccordance with some embodiments of the disclosure.

FIG. 9 is a flow diagram illustrating a method of receiving informationabout characteristics of respective vehicles in accordance with someembodiments of the disclosure.

FIGS. 10A-10P illustrate exemplary ways in which a vehicle identifier isanonymized in accordance with some embodiments of the disclosure.

FIG. 11 is a flow diagram illustrating a method of anonymizing a vehicleidentifier in accordance with some embodiments of the disclosure.

DETAILED DESCRIPTION

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient userinterfaces and mechanisms for user interaction for viewing customizednavigation routes. In some implementations, an electronic devicedisplays customized navigation routes for a respective vehicle based oncharacteristics of the respective vehicle. In some implementations, anelectronic device receives the information on the characteristics of therespective vehicle from an external source (e.g., an applicationassociated with the respective vehicle, a server, a website, etc.). Insome implementations, an electronic device anonymizes a user's licenseplate (e.g., to be used in requesting customized routes from anavigation server). Such techniques can reduce the cognitive burden on auser who uses such devices and/or protect the privacy and/or security ofsensitive incidents while providing navigation routes customized for theuser's vehicles. Further, such techniques can reduce processor andbattery power otherwise wasted on redundant user inputs.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In some embodiments, device 100 is a portable computing system that isin communication (e.g., via wireless communication, via wiredcommunication) with a display generation component. The displaygeneration component is configured to provide visual output, such asdisplay via a CRT display, display via an LED display, or display viaimage projection. In some embodiments, the display generation componentis integrated with the computer system (e.g., an integrated display,touch screen 112, etc.). In some embodiments, the display generationcomponent is separate from the computer system (e.g., an externalmonitor, a projection system, etc.). As used herein, “displaying”content includes causing to display the content (e.g., video datarendered or decoded by display controller 156) by transmitting, via awired or wireless connection, data (e.g., image data or video data) toan integrated or external display generation component to visuallyproduce the content.

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.1 in,and/or IEEE 802.11 ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2 ). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2 ) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2 ). In some embodiments, the electronicdevice is a computer system that is in communication (e.g., via wirelesscommunication, via wired communication) with one or more input devices.In some embodiments, the one or more input devices include atouch-sensitive surface (e.g., a trackpad, as part of a touch-sensitivedisplay). In some embodiments, the one or more input devices include oneor more camera sensors (e.g., one or more optical sensors 164 and/or oneor more depth camera sensors 175), such as for tracking a user'sgestures (e.g., hand gestures) as input. In some embodiments, the one ormore input devices are integrated with the computer system. In someembodiments, the one or more input devices are separate from thecomputer system.

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 )stores device/global internal state 157, as shown in FIGS. 1A and 3 .Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo!Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

In some embodiments, stylus 203 is an active device and includes one ormore electronic circuitry. For example, stylus 203 includes one or moresensors, and one or more communication circuitry (such as communicationmodule 128 and/or RF circuitry 108). In some embodiments, stylus 203includes one or more processors and power systems (e.g., similar topower system 162). In some embodiments, stylus 203 includes anaccelerometer (such as accelerometer 168), magnetometer, and/orgyroscope that is able to determine the position, angle, location,and/or other physical characteristics of stylus 203 (e.g., such aswhether the stylus is placed down, angled toward or away from a device,and/or near or far from a device). In some embodiments, stylus 203 is incommunication with an electronic device (e.g., via communicationcircuitry, over a wireless communication protocol such as Bluetooth) andtransmits sensor data to the electronic device. In some embodiments,stylus 203 is able to determine (e.g., via the accelerometer or othersensors) whether the user is holding the device. In some embodiments,stylus 203 can accept tap inputs (e.g., single tap or double tap) onstylus 203 (e.g., received by the accelerometer or other sensors) fromthe user and interpret the input as a command or request to perform afunction or change to a different input mode.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1 i, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including process 700, 900,and 1100 (FIGS. 7, 9, and 11 ). A computer-readable storage medium canbe any medium that can tangibly contain or store computer-executableinstructions for use by or in connection with the instruction executionsystem, apparatus, or device. In some examples, the storage medium is atransitory computer-readable storage medium. In some examples, thestorage medium is a non-transitory computer-readable storage medium. Thenon-transitory computer-readable storage medium can include, but is notlimited to, magnetic, optical, and/or semiconductor storages. Examplesof such storage include magnetic disks, optical discs based on CD, DVD,or Blu-ray technologies, as well as persistent solid-state memory suchas flash, solid-state drives, and the like. Personal electronic device500 is not limited to the components and configuration of FIG. 5B, butcan include other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “ITL”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“ITD”) in FIG. 5H. The gesture performed with contact 562 is detected ontouch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “ITD”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “ITD”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “ITD”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as device 100, device 300, or device 500.

User Interfaces and Associated Processes Customized Navigation Routes

Users interact with electronic devices in many different manners,including using electronic devices to view and find geographic locationson a map. In some embodiments, a user can request directions from onegeographic location to another geographic location. The embodimentsdescribed below provide ways for displaying customized, suggested routesbetween locations. These routes can be customized based on thecharacteristics of a user's vehicle. This customization enhances theuser's interactions with the electronic device and reduces the amount oftime the user needs to perform operations. Reducing operational timedecreases the power usage of the device and increases battery life forbattery-powered devices.

FIGS. 6A-6FF illustrate exemplary ways in which an electronic devicedisplays customized navigation routes in accordance with someembodiments of the disclosure. The embodiments in these figures are usedto illustrate the processes described below, including the processesdescribed with reference to FIG. 7 . Although FIGS. 6A-6FF illustratevarious examples of ways an electronic device is able to perform theprocesses described below with respect to FIG. 7 , it should beunderstood that these examples are not meant to be limiting, and theelectronic device is able to perform one or more processes describedbelow with reference to FIG. 7 in ways not expressly described withreference to FIGS. 6A-6FF.

FIG. 6A illustrates electronic device 500 displaying user interface 600(e.g., via a display device, via a display generation component, etc.).In some embodiments, user interface 600 is displayed via a displaygeneration component. In some embodiments, the display generationcomponent is a hardware component (e.g., including electricalcomponents) capable of receiving display data and displaying a userinterface. In some embodiments, examples of a display generationcomponent include a touch screen display (such as touch screen 504), amonitor, a television, a projector, an integrated, discrete, or externaldisplay device, or any other suitable display device that is incommunication with device 500.

In some embodiments, user interface 600 is a user interface of a mapapplication (e.g., an application in which a user is able to viewgeographic locations, search for locations, and/or request directionsfrom one location to another). In some embodiments, the map applicationis an application installed on device 500.

In some embodiments, the map application can present maps, routes,location metadata, and/or imagery (e.g., captured photos) associatedwith various geographical locations, points of interest, etc. The mapapplication can obtain map data that includes data defining maps, mapobjects, routes, points of interest, imagery, etc., from a navigationserver. For example, the map data can be received as map tiles thatinclude map data for geographical areas corresponding to the respectivemap tiles. The map data can include, among other things, data definingroads and/or road segments, metadata for points of interest and otherlocations, three-dimensional models of the buildings, infrastructure,and other objects found at the various locations, and/or images capturedat the various locations. The map application can request from anavigation server through a network (e.g., local area network, cellulardata network, wireless network, the Internet, wide area network, etc.)map data (e.g., map tiles) associated with locations that device 500frequently visits. The map application can store the map data in a mapdatabase. The map application can use the map data stored in the mapdatabase and/or other map data received from device 500 to provide themap application features described herein (e.g., display of customizednavigation routes).

In some embodiments, the navigation server can be a software serverconfigured to obtain, generate, and/or store map data. For example, thenavigation server can obtain a lidar generated point cloud (e.g., pointsthat define locations of surfaces of objects in the vicinity of an imagecapture location) for various locations included in the map data. Thenavigation server can generate a three-dimensional model (e.g.,three-dimensional mesh) for each of the various locations using therespective point clouds for the locations. The navigation server canobtain images captured at the various locations (e.g., capturelocations) and use the images to add texture to the three-dimensionalmodel thereby generating a photorealistic three-dimensional imagerepresenting the corresponding location. For example, the capturedimages (e.g., photographs, panorama photographs, etc.) can be stretchedover the surfaces of the three-dimensional model for a particularlocation to generate a photorealistic three-dimensional view of theparticular location. The three-dimensional models and textures (e.g.,captured images, stretched images, images applied to thethree-dimensional model, etc.) can be stored in a map database on thenavigation server and served to user devices (e.g., device 500) toprovide the various features and functions described herein. Thenavigation server can be configured to obtain, generate, and/or storeother map data in the map database.

It is understood that although the description of the figures belowdescribe embodiments in which device 500 determines one or moresuggested routes and/or determines one or more suggested stops, thisdetermination can be performed by the navigation server or by acombination of device 500 and the navigation server, the results ofwhich are provided to device 500 for display in a user interface via adisplay generation component of device 500.

In FIG. 6A, user interface 600 includes a representation of a map. Forexample, in FIG. 6A, user interface 600 includes representations (e.g.,textual and/or graphical presentations) associated with particulargeographic location, including representations of roads, landmarks,businesses, and/or buildings, etc. In some embodiments, a user is ableto search for a respective place or address. For example, in FIG. 6A, auser has performed a search for Destination 1. In some embodiments, inresponse to the search for Destination 1, user interface 600 includesrepresentation 604 at the location on the map corresponding to thelocation of Destination 1, as shown in FIG. 6A.

In some embodiments, the map application searches through a map databasefor locations (e.g., places) that match the search criteria (e.g., forDestination 1). The map application can send a request to a navigationserver to cause the navigation server to search for locations that matchthe search criteria. After obtaining map data corresponding to thesearch criteria, the map application can present a list of places thatmatch the search criteria and/or the user may select one of the placesto cause the place (e.g., address, point of interest, landmark, etc.) tobe presented on user interface 600.

In FIG. 6A, device 500 displays user interface 606 corresponding toDestination 1. In some embodiments, user interface 606 is displayedoverlaid over user interface 600. In some embodiments, user interface606 includes information associated with Destination 1. In FIG. 6A, userinterface 606 includes textual indication 608, button 610, and graphic612. In some embodiments, textual indication 608 includes the name ofDestination 1 and/or the address of Destination 1. In some embodiments,button 610 is selectable to request and/or display navigation directionsto Destination 1 (e.g., from the current location of the electronicdevice or from a respective location provided by a user). In someembodiments, graphic 612 includes an image associated with Destination 1(e.g., an image of the location, an image of the view of Destination 1from the street level, etc.). In some embodiments, user interface 606includes button 614 that is selectable to dismiss user interface 606(e.g., and optionally cease display of the search results).

In FIG. 6A, a user input 603 a is received selecting button 610. In someembodiments, in response to the user input, device 500 displays one ormore suggested routes to travel from the current location of device 500(e.g., represented by location indicator 602) to Destination 1, as shownin FIG. 6B. In FIG. 6B, device 500 displays suggested route 620-1 andsuggested route 620-2. In some embodiments, suggested route 620-1 is thefastest route to Destination 1. In some embodiments, suggested route620-2 is an alternative route to suggested route 620-1. In someembodiments, suggested route 620-1 and/or suggested route 620-2 areselected based on different criteria such as shortest route, fastestroute, avoiding tolls, avoiding highways. In some embodiments, thesuggested routes are selected while taking into consideration thecurrent traffic conditions. In FIG. 6B, because no vehicles arecurrently selected in the map application, the suggested routes areselected without consideration of the characteristics of respectivevehicles (e.g., the driving range of a particular vehicle). Display ofsuggested routes with respect to particular selected vehicles in the mapapplication will be described in further detail below.

In some embodiments, in response to the user input, device 500 displaysuser interface 607, as shown in FIG. 6B. In some embodiments, userinterface 607 includes information for navigating to Destination 1. InFIG. 6B, user interface 607 includes textual indication 609, listing616-1, and listing 616-2. In some embodiments, textual indication 609includes an indication that the suggested routes are for travel toDestination 1 and an indication that the suggested routes are for travelfrom “My Location” to Destination 1. In some embodiments, listing 616-1corresponds to suggested route 620-1 and includes a description thatsuggested route 620-1 is estimated to take 50 minutes to travel, thatsuggested route 620-1 is 43.8 miles in length, and that suggested route620-1 is the fastest route (e.g., by time, optionally including currenttraffic conditions). In some embodiments, listing 616-2 corresponds tosuggested route 620-1 and includes a description that suggested route620-2 is estimated to take 57 minutes to travel, that suggested route620-2 is 44.5 miles in length, and that suggested route 620-2 is analternative route (e.g., alternative to suggested route 620-1). In someembodiments, listing 616-1 and listing 616-2 include button 618-1 andbutton 618-2, respectively, that are selectable to begin navigationalong the respective suggested route. In some embodiments, listing 616-1and listing 616-2 are selectable to display more information about therespective route, as will be described in more detail below.

It is understood that although FIG. 6B illustrates two suggested routesbeing displayed, device 500 may display only one suggested route or maydisplay more than two suggested routes.

In FIG. 6B, a contact 603 b is received on user interface 607. In FIG.6C, an upward swipe 603 c of contact 603 b on user interface 607 isdetected (e.g., an upward swipe from contact 603 b in FIG. 6B). In someembodiments, in response to upward swipe 603 c, user interface 607 isexpanded upwards in accordance with the upward swipe gesture, as shownin FIG. 6C. In some embodiments, expanded user interface 607 includesoptions for selecting one or more vehicles for which to providecustomized suggested routes. For example, in FIG. 6C, expanded userinterface 607 includes vehicle list 622. In some embodiments, vehiclelist 622 includes vehicle option 624-1, vehicle option 624-2, and novehicle option 624-3. In some embodiments, vehicle option 624-1corresponds to a first vehicle that has been registered with (e.g.,added to) the map application and vehicle option 624-2 corresponds to asecond vehicle that has been registered with the map application. Asshown in FIG. 6C, vehicle 1 is a gas vehicle and vehicle 2 is anelectric vehicle. In some embodiments, the no vehicle option 624-3corresponds to no specific vehicle and selection of vehicle option 624-3causes the map application to suggest routes that are selected withoutconsideration of the characteristics of a specific vehicle (e.g., suchas a type of fuel for a particular vehicle or the fuel and/or chargelevel of a particular vehicle), such as described above with respect toFIG. 6B.

In some embodiments, vehicle option 624-1 includes a textual description626-1 of Gas Vehicle 1 (e.g., the name of the vehicle, the make, themodel, etc.). In some embodiments, vehicle option 624-1 includesindication 628-1 of how much fuel (e.g., for a gasoline vehicle) and/orcharge (e.g., for an electric vehicle) the vehicle current has. In someembodiments, the map application receives the current fuel and/or chargeinformation from another application or a server, as will be describedin further detail below with respect to method 900. In some embodiments,vehicle option 624-2 includes a textual description 626-2 of ElectricVehicle 2 (e.g., the name of the vehicle, the make, the model, etc.). Insome embodiments, vehicle option 624-2 includes indication 628-2 of howmuch fuel (e.g., for a gasoline vehicle) and/or charge (e.g., for anelectric vehicle) the vehicle current has. It is understood that if moreor fewer vehicles are registered with the map application, vehicle list622 will include more or fewer vehicles, respectively.

As shown in FIG. 6C, icon 627 (e.g., a check mark) indicates that thecurrently selected option in vehicle list 622 is the no vehicle option624-3, and thus no vehicle is currently selected.

It is understood that although FIG. 6C illustrates two vehicles (Vehicle1 as a gasoline vehicle, and Vehicle 2 as an electric vehicle) beingregistered with the map application, more or fewer vehicles can beregistered with the map application. For example, before the user hasadded any vehicles to the map application (e.g., either manually addedor by linking with a vehicle application, such as described below withrespect to method 900), vehicle list 622 includes no vehicles and onlyincludes the no vehicle option 626-3 (or optionally vehicle list 622 isnot included on user interface 607). In response to adding vehicles,vehicle listing 622 can have one or more vehicles corresponding to thevehicles that have been added. For example, after adding one vehicle,vehicle listing 622 can have one vehicle listing and the no vehiclelisting 626-3. In some embodiments, any of the vehicles in vehiclelisting 622 can be a vehicle of any fuel type (e.g., gasoline vehicle,hybrid vehicle, plug-in hybrid vehicle, hydrogen vehicle, fuel cellvehicle, electric vehicle, solar vehicle, etc.). It is also understoodthat although Vehicle 1 is illustrated as a gasoline vehicle and Vehicle2 is illustrated as an electric vehicle, this is merely exemplary, andVehicle 1 and Vehicle 2 can be a vehicle of any fuel type.

FIGS. 6D-6V illustrate embodiments in which suggested routes aredisplayed based on characteristics of a selected vehicle. For example,the map application (or optionally the navigation server described abovewith which the map application is in communication) is able to determinewhether a selected vehicle requires a stop to recharge or refuel inorder to reach a destination. It is understood that the featuresdescribed below for Gasoline Vehicle 1 and Electric Vehicle 2 are notlimited to only the type of vehicle for which the features weredescribed (e.g., the features described for Gasoline Vehicle 1 are notlimited only to gasoline vehicles, and the features described forElectric Vehicle 2 are not limited to only electric vehicles), and anyor all of the features described for Gasoline Vehicle 1 can be appliedto Electric Vehicle 2 and vice versa. Additionally, the featuresdescribed for either Gasoline Vehicle 1 and Electric Vehicle 2 can beapplied to any type of vehicle with any fuel type (e.g., unleadedgasoline vehicle, diesel gasoline vehicle, hybrid vehicle, plug-inhybrid vehicle, electric vehicle, fuel cell vehicle, hydrogen vehicle,etc.).

In FIG. 6D, a user input 603 d is received selecting vehicle option624-1 corresponding to Gas Vehicle 1. In some embodiments, in responseto user input 603 d, Gas Vehicle 1 becomes the selected vehicle, asshown in FIG. 6E. In FIG. 6E, because suggested routes were provided bythe map application when the user selected Gas Vehicle 1, the suggestedroutes are updated to be customized for Gas Vehicle 1 (optionally ifsuggested routes were not provided by the map application when the userselected Gas Vehicle 1, then no suggested routes are updated). In someembodiments, a customized route for a vehicle is selected based on atleast some of the characteristics of the selected vehicle (e.g., onecharacteristic, two characteristics, etc.). Thus, in FIG. 6E, suggestedroute 620-2 and suggested route 620-3 are selected based on acharacteristic of Gas Vehicle 1. In some embodiments, the suggestedroutes are selected based on the current gas level of Gas Vehicle 1. Insome embodiments, the suggested routes are selected based on theestimated driving range of Gas Vehicle 1 (e.g., the distance that GasVehicle 1 can travel with the current amount of fuel without refueling).

As shown in FIG. 6E, suggested route 620-3 is the primary recommendedroute (e.g., the first listed route and displayed with a prioritizedvisual characterization) and includes suggested stop 632-1. In someembodiments, suggested stop 632-1 is an icon that represents a gasolinestation and indicates that a stop to refuel Gas Vehicle 1 is recommendedand/or required to reach the destination. In some embodiments, suggestedstop 632-1 is placed at a location on suggested route 620-3corresponding to the location of the respective gasoline station. Insome embodiments, a determination that a refueling stop should besuggested is based on the estimated driving range of Gas Vehicle 1. Insome embodiments, if the estimated driving range of Gas Vehicle 1 is notenough to reach the destination, then a suggested stop is recommended.In some embodiments, if Gas Vehicle 1 will reach the destination withless than a threshold amount of fuel (e.g., less than 5%, 10%, 15%, 20%,etc. of fuel) or with less than a threshold number of estimated drivingrange remaining (e.g., less than 5 miles, 10 miles, 20 miles, 30 miles,50 miles, etc.), then a suggested stop is recommended. As will bedescribed below, suggested stop 632-1 is a gasoline station based on thefact that Gas Vehicle 1 requires gasoline for travel, but the suggestedstop can be any type of refilling or recharging station based on thetype of vehicle for which suggested stops are suggested (e.g., electricvehicle, hydrogen vehicle, E85 vehicle, diesel vehicle, etc.).

In some embodiments, listing 616-1 corresponding to suggested route620-3 includes indication 630-1 that indicates that suggested route620-3 includes one stop in Echo Park (e.g., the name of the region atwhich the gas station is located). In some embodiments, listing 616-2corresponding to suggested route 620-2 includes indication 630-2 thatindicates that suggested route 620-2 includes one stop in Pleasantville.In some embodiments, listing 616-1 and listing 616-2 includes anindication of the estimated amount of time to travel along therespective suggested route. In some embodiments, the estimated amount oftime includes the estimated amount of time to refuel the vehicle to thesuggested level. In some embodiments, suggested route 620-2 does notinclude a representation or icon of a suggested stop even thoughsuggested route 620-2 does include a suggested stop. In someembodiments, only the first listed (e.g., most recommended, or the routethat is currently selected or highlighted) suggested stop includes iconsof suggested stops and other suggested routes do not include an icon ofsuggested stops even if the suggested route includes suggested stops(e.g., any or all of the other suggested stops). In some embodiments,all displayed suggested routes include an icon or indication ofsuggested stops (e.g., and not just the first suggested route). As shownin FIG. 6E, in some embodiments, one or more of the customized suggestedroutes is the same as the non-customized suggested routes. For example,suggested route 620-2 in FIG. 6E is the same as suggested route 620-3 inFIG. 6B (e.g., optionally except that suggested route 620-2 in FIG. 6Eincludes a suggested stop). In some embodiments, suggested route 620-3is a route that would not otherwise be suggested when no vehicle isselected (e.g., as in FIG. 6B).

In FIG. 6E, user input 603 e is received selecting listing 616-1corresponding to suggested route 620-3. In some embodiments, in responseto user input 603 e, device 500 displays user interface 634, as shown inFIG. 6F. In some embodiments, user interface 634 includes one or morestep-by-step directions for travelling from the current location ofdevice 500 to Destination 1 via suggested route 620-3. In FIG. 6F, userinterface 634 includes step 636-1 to step 636-7 for travelling from thestarting location to the destination location.

In some embodiments, one or more of the steps includes an indication ofan amount of fuel and/or charge that the vehicle will or should havewhen the vehicle reaches or is following the respective step. Forexample, step 636-1 corresponding to the starting location (e.g., thestarting step) includes indication 638-1 of the estimated amount of gasthat Gas Vehicle 1 will have at the starting location. In someembodiments, indication 638-1 includes an indication of the currentamount of gas (e.g., because step 636-1 is the first step). In someembodiments, step 636-4 corresponding to the suggested stop (e.g.,suggested stop 632-1 in Echo Park at a gas station to refuel) includesan indication 638-2 of the recommended amount of fuel to fill GasVehicle 1 up to in order to reach the destination (optionally to reachthe destination with the threshold amount of fuel or remaining drivingrange). In some embodiments, step 636-7 corresponding to the arrivalstep at the destination includes indication 638-3 that indicates theestimated amount of fuel that Gas Vehicle 1 will have upon arriving atthe destination (e.g., 5/16 of a tank). It is understood that more orfewer steps can include indications of an estimated amount of fuel(e.g., zero, one, or more steps include indications of an estimatedamount of fuel optionally while zero, one or more other steps do notinclude indications of an estimated amount of fuel) and any of steps636-1 to 636-7 can include an indication of an estimated amount of fuelwhen arriving at or following the respective step.

In FIG. 6F, user input 603 f is received selecting the “Done” button. Insome embodiments, in response to user input 603 f, user interface 634 isdismissed (e.g., ceased to be displayed), as shown in FIG. 6G.

In FIG. 6G, a contact 603 g is received on user interface 607. In FIG.6H, an upward swipe 603 h of contact 603 g on user interface 607 isdetected (e.g., an upward swipe from contact 603 g in FIG. 6G) causingdisplay of expanded user interface 607. In FIG. 6I, while displayingexpanded user interface 607, a user input 603 i is received selectinglisting 626-2 corresponding to Electric Vehicle 2. In some embodiments,in response to user input 603 i, Electric Vehicle 2 becomes the selectedvehicle, as shown in FIG. 6J. In some embodiments, because suggestedroutes were displayed by the map application when user input 603 i wasreceived in FIG. 6I, the suggested routes are updated to be customizedfor Electric Vehicle 2. For example, in FIG. 6J, user interface 600includes suggested route 620-1 and suggested route 620-2. As shown,suggested route 620-1 and suggested route 620-2 are the same routessuggested in FIG. 6B because Electric Vehicle 2 has enough charge toreach the destination (e.g., 73% charge). Thus, even though device 500takes into account the charge status of Electric Vehicle 2, thesuggested routes can optionally be the same suggested routes as whendevice 500 does not take into account charge status (e.g., when device500 suggests routes when no vehicle is selected).

FIG. 6K illustrates an embodiment in which Electric Vehicle 2 does nothave enough charge to reach the destination (e.g., 23% charge). In suchembodiments, user interface 600 includes suggested route 620-4 andsuggested route 620-5. In some embodiments, suggested route 620-4includes suggested stop 632-2 corresponding to a recommended stop torecharge Electric Vehicle 2 at an electric vehicle charging station. Insome embodiments, suggested stop 632-2 is recommended because ElectricVehicle 2 does not have enough charge to reach the destination (oroptionally will not have enough charge to reach the destination with athreshold amount of remaining charge or remaining driving range). Insome embodiments, as will be described in more detail below with respectto method 900, suggested stop 632-2 is selected based on the chargingstation network that is compatible with Electric Vehicle 2. In someembodiments, suggested stop 632-2 in FIG. 6K is an electric vehiclecharging station based on the fact that Electric Vehicle 2 requireselectric charge for travel, but the suggested stop can be any type ofrefilling or recharging station based on the type of vehicle for whichsuggested stops are suggested (e.g., gasoline vehicle, hydrogen vehicle,E85 vehicle, diesel vehicle, etc.).

As shown in FIG. 6K, suggested route 620-4 is a different route thansuggested route 620-1 and suggested route 620-2 because device 500 hasdetermined that a recharging stop is required. Thus, suggested route620-4 navigates the user to a suggested recharging stop beforenavigating the user to the destination. In some embodiments, suggestedroute 620-4 is different than suggested route 620-3 because ElectricVehicle 2 requires an electric vehicle recharging stop rather than agasoline station stop. Thus, device 500 is able to take into account thecharge status of Electric Vehicle 2 as well as the type of stop requiredbased on the fuel type of Electric Vehicle 2 (e.g., electricity ratherthan gasoline). Similarly, suggested route 620-5 is different fromsuggested route 620-1, suggested route 620-2 and suggested route 620-3because it is an alternative route that also includes a stop at anelectric vehicle charging station. In some embodiments, any of thesuggested routes for Electric Vehicle 2 can have a similar route as anyof the suggested routes discussed above for Gas Vehicle 1 or when novehicle is selected, but optionally include a stop at an electricvehicle charging station, for example, if a compatible electric vehiclecharging station happens to be along one of the routes that otherwisewould have been suggested to the user for Electric Vehicle 2.

In some embodiments, listing 616-1 corresponding to suggested route620-4 includes indication 630-1 that indicates that suggested route620-3 includes one stop in Echo Park (e.g., the name of the region atwhich the charging station is located). In some embodiments, listing616-2 corresponding to suggested route 620-5 includes indication 630-2that indicates that suggested route 620-5 includes one stop in SilentHill. In some embodiments, suggested route 620-5 does not include arepresentation or icon of a suggested stop even though suggested route620-5 does include a suggested stop. In some embodiments, only the firstlisted (e.g., most recommended route or the route that is currentlyselected or highlighted) suggested stop includes icons of suggestedstops and other suggested routes do not include an icon of suggestedstops even if the suggested route includes suggested stops (e.g., any orall of the other suggested stops). In some embodiments, all displayedsuggested routes include an icon or indication of suggested stops (e.g.,and not just the first suggested route). As shown in FIG. 6K, theindication (e.g., icon) of the suggested stop 632-2 is a representationof an electric vehicle charging station and is a different icon thansuggested stop 632-1 shown in FIG. 6G that is a representation of a gasstation. In some embodiments, the icon representing a suggested stopalong a route is the same regardless of whether the suggested stop is anelectric vehicle charging station or a gasoline station.

In FIG. 6K, user input 603 k is an input that selects listing 616-1corresponding to suggested route 620-4. In some embodiments, in responseto user input 603 k, device 500 displays user interface 634, as shown inFIG. 6L. In some embodiments, user interface 634 includes one or morestep-by-step directions for travelling from the current location or aselected starting location of device 500 to Destination 1 via suggestedroute 620-4. In FIG. 6L, user interface 634 includes step 636-1 to step636-6 for travelling from the starting location to the destinationlocation.

In some embodiments, as illustrated in FIG. 6L, one or more of the steps636-1 to 636-6 include an indication of an amount of charge thatElectric Vehicle 2 will or should have when the vehicle reaches thelocation of the respective step (e.g., if the vehicle is following theroute as planned). For example, step 636-1 corresponding to the startinglocation (e.g., the starting step) includes indication 638-1 of theestimated amount of charge that Electric Vehicle 2 will have at thestarting location. In some embodiments, indication 638-1 includes anindication of the current amount of charge (e.g., because step 636-1 isthe first step). In some embodiments, step 636-4 corresponding to thesuggested stop of FIG. 6K (e.g., suggested stop 632-2 in Echo Park at anelectric vehicle charging station to recharge) includes an indication638-2 of the recommended amount of charge to recharge Electric Vehicle 2up to in order to reach the destination (optionally to reach thedestination with the threshold amount of charge or remaining drivingrange). In some embodiments, step 636-6 corresponding to the arrivalstep at the destination includes indication 638-3 that indicates theestimated amount of charge that Electric Vehicle 2 will have uponarriving at the destination (e.g., 38% battery remaining). It isunderstood that more or fewer steps can include indications of anestimated amount of charge and any of steps 636-1 to 636-6 can includean indication of an estimated amount of charge when arriving at orfollowing the respective step.

In FIG. 6L, user input 603 l is received selecting the “Done” button. Insome embodiments, in response to user input 603 l, user interface 634 isdismissed (e.g., ceased to be displayed), as shown in FIG. 6M. In FIG.6M, a user input 603 m is received selecting button 618-1 for beginningnavigation using suggested route 620-4. In some embodiments, in responseto user input 603 m, device 500 begins navigation mode and displays userinterface 640, as shown in FIG. 6N.

In some embodiments, navigation mode includes displaying step-by-stepand/or turn-by-turn directions to travel along a respective route. Insome embodiments, the step-by-step and/or turn-by-turn directions areprovided based on the location of the device to provide the user withlive directions to reach the destination. In FIG. 6N, user interface 640includes instructions 642 and instructions 644. In some embodiments,instructions 642 includes textual instructions corresponding to thecurrently displayed step. For example, in FIG. 6N, instructions 642instruct the user to begin driving on Main St. In some embodiments,instructions 644 provide additional instructions associated with thedisplayed step or provides a preview of the next step. For example, inFIG. 6N, instructions 644 indicates that the next step is to turn lefton Ocean Ave. As shown in FIG. 6N, any of instructions 642 and/or 644can include an icon representative of the step (e.g., a turn icon, astart icon, etc.). In some embodiments, instructions 644 is notdisplayed for certain steps or for all steps (e.g., if additionalinformation is not necessary).

In some embodiments, user interface 640 includes a representation of themap that includes the current position of device 500, illustrated bylocation indicator 646. As shown in FIG. 6N, location indicator 646indicates the current position of device 500 (e.g., is located on therepresentation of the map corresponding to the current location ofdevice 500) and/or the orientation of device 500 (e.g., the arrow inlocation indicator 646 is facing in the direction of the orientation ofdevice 500). In some embodiments, user interface 640 includes route 648corresponding to suggested route 620-4. In some embodiments, therepresentation of the map is oriented such that the map is facing thedirection that device 500 is facing. For example, in FIG. 6N, if device500 is facing south, then the representation of the map is oriented suchthat south is upwards.

In some embodiments, user interface 640 includes user interface 650 thatis displayed overlaid over user interface 640. In some embodiments, userinterface 650 provides general information of suggested route 620-4. Forexample, in FIG. 6N, user interface 650 includes indication 652,indication 654, and button 656. In some embodiments, indication 652displays the estimated time of arrival at the next stop (e.g., thesuggested stop, the destination, or a user-selected stop along thesuggested route). In some embodiments, indication 654 displays theestimated amount of charge that Electric Vehicle 2 will have uponarrival at the next stop. In some embodiments, button 656 is selectableto end navigation mode (e.g., to stop providing step-by-step orturn-by-turn instructions to reach the destination).

FIG. 6O illustrates an embodiment in which the user has traveled alongsuggested route 620-4 and is approaching the suggested charging stopalong suggested route 620-4. In some embodiments, device 500 determinesthat the user has traveled along suggested route 620-4 and isapproaching the suggested charging stop (e.g., suggested stop 632-2 fromFIG. 6K, represented by representation 660) using one or more devicelocation mechanisms or processes (e.g., using a GPS locator on device500, etc.). In FIG. 6O, instructions 642 is updated to indicate that thesuggested charging stop is 400 feet ahead and on the left side of theroad. In some embodiments, instructions 644 is updated to provideadditional information about the suggested charging stop (e.g., that thecharging station is located on the first floor). In some embodiments, ifthe suggested stop is to refuel at a gasoline station (e.g., for agasoline vehicle), instructions 644 can be updated to provide additionalinformation about the gasoline station (e.g., which pump to use, whichgrade of gas to use, where the pumps are located, etc.).

In some embodiments, user interface 640 includes route 648 correspondingto the upcoming route. In some embodiments, user interface 640 includesroute 658 corresponding to the route that was traversed. Between route648 and route 658, there may be a representation (e.g., indicator 646)of the current location of the user's vehicle. In some embodiments, userinterface 640 includes representation 660 corresponding to the suggestedstop (e.g., suggested stop 632-2 from FIG. 6K). In some embodiments,representation 660 is displayed at a location on the representation ofthe map corresponding to the location of the suggested stop. As shown inFIG. 6O, representation 660 is an icon of an electric vehicle chargingstation. In some embodiments, representation 660 includes a textualdescription of the suggested stop (e.g., the name of the suggested stop,the name of the charging station, the charging network associated withthe charging station, etc.).

FIG. 6P illustrates an embodiment in which the user has arrived at thesuggested charging stop (or optionally within a threshold distance fromthe suggested charging stop, such as 50 feet, 100 feet, 300 feet, 500feet, 1500 feet, etc.). In some embodiments, instructions 642 is updatedto indicate that the user has arrived at the suggested stop. In someembodiments, instructions 644 is updated to suggest that the user useAdapter 1 to convert the plug used by Electric Vehicle 2 to a plug typethat is compatible with the charging station. In some embodiments,determination that Adapter 1 is required to convert the plug typeinstalled on Electric Vehicle 2 to a plug type that is compatible withthe charging station is based on information received about ElectricVehicle 2 as described below with respect to method 900 (e.g.,information about the compatible plug types, information about availableadapters, etc.). It is understood that providing information regardingrequired adapters can be applied to vehicles of other fuel types (e.g.,gasoline vehicles, electric vehicles, hybrid vehicles, plug-in hybridvehicles, etc.).

FIG. 6Q illustrates an embodiment in which device 500 has determinedthat Electric Vehicle 2 is being charged. In some embodiments, device500 receives information about the charging status from a sourceexternal to the map application (e.g., an application other than the mapapplication, or a server external to device 500) as described below withrespect to method 900. In some embodiments, instructions 642 is updatedto instruct the user to charge Electric Vehicle 2 to at least 53% andthat the charging is estimated to take 15 minutes. In some embodiments,the estimated remaining charge time is determined based on informationreceived from the source external to the map application.

In some embodiments, in response to determining that Electric Vehicle 2is being charged, user interface 640 is updated to display route 648corresponding to the forward route to reach the destination. In FIG. 6Q,user interface 650 is updated to include button 662. In someembodiments, button 662 is selectable to pause navigation mode (e.g.,while the vehicle is charging). In some embodiments, pausing navigationmode returns the map application to a browsing mode in which a user isable to interact with the representation of the map and search forlocations (and optionally provides for easy resumption of navigationmode, as described below), such as shown in FIG. 6A. In FIG. 6Q, a userinput 603 q is received selecting button 662. In some embodiments, inresponse to user input 603 q, device 500 pauses (e.g., ceases, ends, orstops) navigation mode (and optionally displays user interface 600, suchas in FIG. 6A).

FIG. 6R illustrates an exemplary lock or wake screen user interface 664while Electric Vehicle 2 is being charged (e.g., optionally after theuser has paused navigation mode via selection of button 662, after theuser has locked device 500 or placed device 500 in a low power mode, orafter navigating away from a user interface of the map application, suchas user interface 600). A lock or wake screen user interface (e.g., suchas user interface 664) is a user interface that is initially displayedupon waking device 500 after waking device 500 from a low power mode. Insome embodiments, while navigation is paused (e.g., previously ceased,ended, or stopped) and while Electric Vehicle 2 is being charged, device500 displays notification 668 that includes the charging status of thevehicle and/or the remaining charging time. In FIG. 6R, notification 668indicates that there is five minutes of estimated time remaining toreach the suggested charge level. In some embodiments, the suggestedcharge level is selected based on the remaining distance to thedestination (e.g., the amount of charge required to reach thedestination, the amount of charge required to reach the destination witha threshold amount of remaining charge and/or remaining driving range).In some embodiments, notification 668 is periodically updated (e.g.,every 10 seconds, 30 seconds, 1 minute, 5 minutes, 10 minutes, etc.) toindicate the estimated remaining time to charge the vehicle to thesuggested charge level. In some embodiments, notification 668 indicatesthe current charge level (or gasoline level for a gasoline vehicle, orany other relevant fuel amount for vehicles of other fuel types).

In some embodiments, notification 668 is displayed on any user interfaceand is not limited to only a lock or wake screen user interface. Forexample, notification 668 can be displayed while device 500 isdisplaying a system user interface (e.g., the home screen userinterface, an application launching user interface, a settings userinterface) or a user interface of an application. In some embodiments,notification 668 can be displayed on a notification user interface(e.g., a user interface that includes one or more active notifications).In some embodiments, notification 668 is persistent and remainsdisplayed on the lock or wake screen user interface (optionally and onthe notification user interface) while Electric Vehicle 2 is beingcharged. In some embodiments, notification 668 is automaticallydismissed (e.g., removed from lock or wake screen user interface 664and/or the notification user interface) in accordance with adetermination that Electric Vehicle 2 has stopped charging. In someembodiments, notification 668 can be manually dismissed in response to auser input requesting dismissal of notification 668.

FIG. 6S illustrates notification 668 when device 500 determines thatElectric Vehicle 2 has reached the suggested charge level. In someembodiments, notification 668 indicates that Electric Vehicle 2 is readyto continue travelling towards the destination. In some embodiments,notification 668 indicates that Electric Vehicle 2 has reached thesuggested charge level. In some embodiments, notification 668 indicatesthe current charge level.

In some embodiments, selection of notification 668 (e.g., while ElectricVehicle 2 is charging or after Electric Vehicle 2 has completedcharging) initiates a process to display the map application (e.g., userinterface 600) and/or to resume navigation (e.g., optionally afterdevice 500 has been unlocked). In some embodiments, if Electric Vehicle2 has charged beyond the suggested level, then notification 668 canindicate that Electric Vehicle 2 has charged beyond the level requiredand that Electric Vehicle 2 is ready to continue along the suggestedroute.

FIG. 6T illustrates an exemplary user interface 600 of the mapapplication while Electric Vehicle 2 is being charged, such as inresponse to a user selection of button 662. In some embodiments, userinterface 606 includes an indication 672 to charge Electric Vehicle 2for another 15 minutes. In some embodiments, indication 672 isperiodically updated (e.g., every 10 seconds, 30 seconds, 1 minute, 5minutes, 10 minutes, etc.) to indicate the estimated remaining time tocharge the vehicle to the suggested charge level. In some embodiments,indication 672 indicates the current charge level. In some embodiments,for vehicles of other fuel types, indication 672 indicates the currentfuel level (e.g., gasoline level for gasoline vehicles, etc.).

FIG. 6U illustrates indication 672 when device 500 determines thatElectric Vehicle 2 has reached the suggested charge level. In someembodiments, indication 672 indicates that Electric Vehicle 2 is readyto continue travelling towards the destination. In some embodiments,indication 672 indicates that Electric Vehicle 2 has reached thesuggested charge level. In some embodiments, indication 672 isselectable to resume navigation mode (e.g., and optionally display userinterface 640).

In FIG. 6U, a user input 603 u is received selecting indication 672. Insome embodiments, in response to user input 603 u, device 500 resumesnavigation mode of suggested route 620-4 and displays user interface640, as shown in FIG. 6V. Similarly, navigation mode of suggested route620-4 is optionally resumed in response to selection of notification 668shown in FIG. 6S. In some embodiments, selection of notification 668 orindication 672 before the vehicle has reached the suggested charge leveldoes not cause resumption of navigation mode. In some embodiments,selection of notification 668 or indication 672 before the vehicle hasreached the suggested charge level does cause resumption of navigationmode (but optionally could cause the addition of another suggested stop,such as described below with respect to FIG. 6V).

FIG. 6V illustrates an embodiment in which device 500 determines that a(or another) refueling and/or recharging stop is required to reach thedestination while in navigation mode. In some embodiments, a refuelingand/or recharging stop was not previously recommended but based onupdated information, a refueling and/or recharging stop is nowrecommended. For example, based on updated information, device 500determines that Electric Vehicle 2 will not reach the destination (oroptionally will reach the destination with less than a threshold amountof charge or less than a threshold amount of driving range remaining).In some embodiments, the updated information is an updated estimateddriving range of Electric Vehicle 2 and/or an updated charge level ofElectric Vehicle 2, such as described below with respect to method 900.For example, in FIG. 6V, device 500 determines that Electric Vehicle 2only has 10% charge remaining and may not reach the destination. In someembodiments, a suggested stop is required if the original estimateddriving range was not accurate, because the driving economy of thevehicle changed (e.g., due to aggressive or spirited driving), becauseElectric Vehicle 2 did not follow the suggested route, or any otherpotential reason.

In some embodiments, in response to determining that a refueling and/orrecharging stop is required, device 500 determines (or theabove-described navigation server determines) the appropriate suggestedstop and determines whether the route should be modified. For example,in FIG. 6V, user interface 640 is updated to display route 648 thatincludes a suggested stop 684. As shown in FIG. 6V, route 648 is amodified route to the same destination that includes the suggested stop.In some embodiments, an indication is displayed that route 648 is asuggested route. In some embodiments, route 682 is displayedcorresponding to the original suggested route (e.g., without thesuggested stop). In some embodiments, user interface 674 is displayedindicating that a suggested stop is recommended and requestingconfirmation of whether to add the suggested stop to the navigationroute. In some embodiments, user interface 674 includes textualindication 676 that indicates that a charging stop is required orsuggested because there is not enough charge to reach the destination.In some embodiments, user interface 674 includes button 678 that isselectable to dismiss user interface 674, to decline adding thesuggested stop, and to continue along the original route (e.g., alongroute 682). In some embodiments, user interface 674 includes button 680that is selectable to confirm addition of the suggested stop and tonavigate along route 648 (including stopping at the suggested stop). Insome embodiments, for vehicles of other fuel types (e.g., gasoline,hydrogen, E85, etc.), device 500 can display suggested stops to rechargeand/or refuel at a compatible station.

FIGS. 6W-6FF illustrate embodiments in which suggested routes areselected based on the characteristics of respective vehicles withrespect to driving restrictions. In FIG. 6W, device 500 displays userinterface 600 of the map application and user interface 606. In FIG. 6W,user interface 600 does not include any suggested routes or drivingdirections and is optionally a default user interface of the mapapplication (e.g., in a browsing state) that includes location indicator602. In some embodiments, user interface 606 includes search field 670.In some embodiments, user interface 606 includes indication 686. In someembodiments, indication 686 is displayed in accordance with adetermination that the current location of device 500 is within or neara geographic region in which a driving restriction exists.

In the embodiments illustrated in FIGS. 6W-6FF, the respective drivingrestriction is based on the license plate of the vehicle, but it isunderstood that any driving restriction is possible. In someembodiments, a driving restriction corresponds to a restriction thatdefines that a certain set of vehicles may travel without restrictionand a second set of vehicles are restricted from travel. In someembodiments, other restrictions are possible (e.g., a first set ofvehicles must follow a certain set of rules or regulations while asecond set follows a different set of rules or regulations, or allvehicles with a certain characteristic(s) are restricted from travel,etc.). For example, if a particular region or set of roads arecontrolled by a driving restriction, certain vehicles with certaincharacteristics defined by the restriction may be restricted fromtraveling within the region (or on the roads), while other vehicleswithout those certain characteristics may not be restricted fromtraveling within the region (or on the roads). For example, arestriction can exist in which odd numbered license plates (e.g.,vehicles with license plates that end in an odd number) are prohibitedfrom driving in a particular location during particular times and dateswhile even numbered license plates (e.g., vehicles with license platesthat end in an even number) are not prohibited from driving at any time(or are prohibited from driving in the particular location during othertimes). Another example of a driving restriction can be that vehiclesover a particular gross weight are prohibited from driving on aparticular highway during business hours, while vehicles under the grossweight threshold are not prohibited from driving on the highway.

In some embodiments, indication 686 includes affordance 688 that isselectable to provide one or more vehicle license plates to the mapapplication. In some embodiments, indication 686 is displayed only if nolicense plates have yet been provided to the map application. Thus, insome embodiments, indication 686 is not displayed after the user adds afirst license plate to the map application (optionally even if thecurrent location of device 500 is within or near a geographic region inwhich a driving restriction exists). In some embodiments, indication 686can be displayed even if the user has added a license plate to the mapapplication if the current location of device 500 is within or near ageographic region in which a driving restriction that is not based on avehicle's license plate exists and suggest to the user to provide othercharacteristic information for their vehicle (e.g., based on height,width, number of axles, weight, or any other suitable characteristic ofthe vehicle, etc.). In some embodiments, the process for adding avehicle, registering a vehicle, and/or providing license plateinformation is similar to the process described below with respect toFIGS. 8D-8H.

FIG. 6X illustrates an embodiment in which suggested routes are providedto the user with respect to a driving restriction. In some embodiments,if the user requests directions to a destination and one or more routesrequire the user to travel through a region that is subject to a drivingrestriction, user interface 600 includes an indication 698 of the regionthat is subject to the driving restriction. In some embodiments,indication 698 is a visual element that visually differentiates thegeographic region that is subject to the driving restriction from theareas that are not subject to a driving restriction (e.g., with a greycolor, with a fill pattern, etc.).

In some embodiments, as shown in FIG. 6X, user interface 600 includessuggested route 620-6 and suggested route 620-7. In some embodiments,suggested route 620-6 travels through the geographic region that issubject to the driving restriction. In some embodiments, suggested route620-6 includes indicator 692 on the border of the geographic region thatis subject to the driving restriction to indicate that the user maybecome subject to the driving restriction at the location indicated byindicator 692. In some embodiments, label 690-1 corresponding tosuggested route 620-6 indicates that suggested route 620-6 is thefastest route (and is estimated to take 30 minutes) and includes an iconthat indicates that a driving restriction may apply to the user'svehicle.

In some embodiments, suggested route 620-7 travels around the geographicregion that is subject to the driving restriction and does not includean indicator that indicates that the user may become subject to thedriving restriction. In some embodiments, label 690-2 corresponding tosuggested route 620-7 indicates that suggested route 620-7 avoids thedriving restriction. As shown in FIG. 6X, no vehicle is currentlyselected, so device 500 does not have license plate information for thevehicle that the user intends to use to travel along the suggestedroutes. Thus, in some embodiments, device 500 provides at least oneroute that is selected without regard to the driving restriction (e.g.,the fastest route, such as suggested route 620-6) and at least one routethat is selected to avoid the driving restriction (e.g., the fastestroute that avoids the driving restriction, such as suggested route620-7). In some embodiments, only one suggested route is displays (e.g.,only the fastest route without regard to the restriction or only thefastest route that avoids the restriction).

In some embodiments, user interface 606 includes listing 616-1corresponding to suggested route 620-6 and listing 616-2 correspondingto suggested route 620-7. In some embodiments, listing 616-1 includesindication 630-1 that indicates that suggested route 620-6 is subject todriving restrictions. In some embodiments, indication 630-1 includeslink 694 that is selectable to display details about the respectivedriving restriction that applies in the respective geographic region. Insome embodiments, listing 616-2 does not include an indication thatsuggested route 620-7 is subject to driving restrictions, but includesan indication that suggested route 620-7 avoids the driving restrictionto which suggested route 620-6 is subject.

In some embodiments, if suggested route does not pass through or passnear a restricted region, then map user interface 600 does not includeindication 698 of the region that is subject to the driving restriction.For example, in the embodiment illustrated in FIG. 6B, no drivingrestrictions apply in the region displayed by the representation of themap, and thus device 500 does not display an indication of a drivingrestriction (e.g., does not include indication 698, indication 630-1and/or link 694).

In FIG. 6Y, user input 603 y is received selecting link 694corresponding to a request to display more information about the drivingrestriction. In some embodiments, in response to user input 603 y,device 500 updates user interface 607 to display information about thedriving restriction, as shown in FIG. 6Z. In some embodiments, updateduser interface 607 includes description 696 that describes the drivingrestriction that applies, optionally including description of what therestriction is and which vehicles are subject to the restrictions. Forexample, in FIG. 6Z, description 696 indicates that vehicles withlicense plate numbers that end in an odd number are prohibited fromdriving inside the restricted region (e.g., Downtown Pleasanton) onTuesdays and Thursdays between 7:00 AM and 6:30 PM. In some embodiments,as will be described in further detail below, device 500 is able todetermine whether a particular car is subject to the restriction and thetimes at which the car is subject to the restriction, and selectsuggested routes based on the determination.

In FIG. 6AA, an upward swipe 603 aa of a contact on user interface 607is detected (e.g., an upward swipe from a contact on user interface 607illustrated in FIG. 6Y), causing expansion of user interface 607 (e.g.,similar to FIG. 6C). Similar to described above with respect to FIG. 6C,expanded user interface 607 includes vehicle list 622. In someembodiments, vehicle list 622 includes vehicle option 624-1, vehicleoption 624-2, and no vehicle option 624-3. In some embodiments, vehicleoption 624-1 corresponds to a first vehicle that has been registeredwith (e.g., added to) the map application (e.g., the user has providedlicense plate information for the first vehicle to the map application)and vehicle option 624-2 corresponds to a second vehicle that has beenregistered with the map application (e.g., the user has provided licenseplate information for the second vehicle to the map application). Asshown in FIG. 6AA, vehicle 1 is a gas vehicle and vehicle 2 is anelectric vehicle. In some embodiments, no vehicle option 624-3corresponds to no specific vehicle and selection of vehicle option 624-3causes the map application to suggest routes that are selected withoutconsideration of the characteristics of a specific vehicle (e.g.,without respect to whether a particular car is subject to arestriction), such as described above with respect to FIG. 6Y.

In FIG. 6BB, a user input 603 bb is received selecting vehicle option624-2 corresponding to Electric Vehicle 2. In some embodiments, inresponse to user input 603 bb, Electric Vehicle 2 becomes the selectedvehicle, as shown in FIG. 6CC. In FIG. 6CC, because suggested routeswere displayed when the user selected Electric Vehicle 2, the suggestedroutes are updated to be customized for Electric Vehicle 2. In someembodiments, a customized route for a vehicle is selected based on thelicense plate information of Electric Vehicle 2 (e.g., additionally oralternatively to vehicle characteristics described with reference toFIGS. 6A-6V). For example, device 500 is able to determine, based on theprovided license plate information of Electric Vehicle 2, whetherElectric Vehicle 2 is permitted to drive in the restricted region orprohibited from driving in the restricted region (e.g., based on thedriving restriction rules, optionally at the current time or optionallyat a future time selected by the user). In FIG. 6CC, Electric Vehicle 2has an odd license plate number (e.g., the last number of the licenseplate is an odd number), and thus would be prohibited from drivinginside Downtown Pleasanton on Tuesdays and Thursdays between 7:00 AM and6:30 PM. Thus, in some embodiments, if the current time and day isTuesday or Thursday between 7:00 AM and 6:30 PM, then the suggestedroutes are selected to avoid the restriction region (e.g., at least onesuggested route avoids the restriction). For example, suggested route620-7 is now the first suggested route (e.g., displayed first in userinterface 607 and displayed on the map user interface with a prioritizedvisual characteristic). In some embodiments, one or more of thesuggested routes travel through the restricted region even thoughElectric Vehicle 2 is prohibited from driving in the restricted region.For example, suggested route 620-6 is the fastest route, but becausesuggested route 620-6 travels through the restricted region, suggestedroute 620-6 is not displayed first and is displayed in the map userinterface with a de-prioritized visual characteristic.

In some embodiments, a user input 603 cc is received selecting button618-1 corresponding to a request to begin navigation mode usingsuggested route 620-6, as shown in FIG. 6CC. Thus, in some embodiments,even though the selected vehicle (e.g., Electric Vehicle 2) isprohibited from driving inside the restricted region, a user is able tobegin navigation along a route that takes the user into the restrictedregion. In some embodiments, in response to user input 603 cc, device500 begins navigation mode and displays user interface 640, as shown inFIG. 6DD.

FIG. 6DD illustrates an embodiment in which the user has traveled alongsuggested route 620-6 and is approaching the boundary of the restrictedregion (e.g., within 50 feet, 100 feet, 300 feet, 500 feet, 1000 feet,3000 feet, etc.). In some embodiments, device 500 determines that theuser has traveled along suggested route 620-6 and is approaching theboundary of the restricted region using one or more device locationmechanisms or processes (e.g., using a GPS locator on device 500, etc.).In FIG. 6DD, the restricted region is visually differentiated from thenon-restricted region (e.g., similar to indication 698 in FIG. 6X). Insome embodiments, indication 646 is displayed at or near the boundary ofthe restricted region indicating the point at which the restrictedregion begins. In some embodiments, device 500 displays user interface699 in response to the device 500 coming within a threshold distance(e.g., 100 feet, 300 feet, 500 feet, 1000 feet, 3000 feet, etc.) of thelocation of the restriction boundary, and user interface 699 optionallyincludes description 697 that provides a warning that the restrictedregion is ahead. In some embodiments, description 697 includes a briefdescription of the restriction (e.g., that odd numbered plates areaffected).

As shown above, in some embodiments, although device 500 providesindications and/or warnings that the user is about to enter a restrictedregion, device 500 does not prevent the user from entering therestricted region or limit the navigational or mapping functionalitiesof the device as the user enters the restricted region or while the useris in the restricted region. Thus, in some embodiments, the deviceprovides the user with information regarding the restricted region, butallows the user to make the decision of whether to enter the restrictedregion.

FIGS. 6EE-6FF illustrate an embodiment in which suggested routes areselected for a vehicle that that is not prohibited from driving within arestricted region. In FIG. 6EE, a user input 603 ee is receivedselecting listing 624-1 from vehicle list 622 on expanded user interface606. In some embodiments, in response to user input 603 ee, Gas Vehicle1 becomes the selected vehicle, as shown in FIG. 6FF. In FIG. 6FF,because suggested routes were displayed when the user selected GasVehicle 1, the suggested routes are updated to be customized for GasVehicle 1. In some embodiments, a customized route for a vehicle isselected based on the license plate information of Gas Vehicle 1. Forexample, device 500 is able to determine, based on the provided licenseplate information of Gas Vehicle 1, whether Gas Vehicle 1 is permittedto drive in the restricted region or prohibited from driving in therestricted region (e.g., based on the driving restriction rules,optionally at the current time or optionally at a future time selectedby the user). In FIG. 6FF, Gas Vehicle 1 has an even license plate(e.g., the last number of the license plate is an even number) and thusis not prohibited from driving inside Downtown Pleasanton. Thus, in someembodiments, the suggested routes are selected without regard to therestriction of the restricted region. For example, suggested route 620-6is the first suggested route (e.g., displayed first in user interface606 and displayed on the map user interface with a prioritized visualcharacteristic), optionally because suggested route 620-6 is the fastestroute. In some embodiments, suggested route 620-8 is an alternativeroute (e.g., alternative to suggested route 620-6). As shown in FIG.6FF, both suggested route 620-6 and suggested route 620-8 travel intoand/or through the restricted region. In some embodiments, userinterface 600 does not display any indication that the suggested routesare subject to the restricted region. In some embodiments, userinterface 600 still includes indicator 698 that indicates the area ofthe restricted region. In some embodiments, one or more of the suggestedroutes for Gas Vehicle 1 are the same routes as shown in FIG. 6X (e.g.,suggested route 620-6 corresponding to the fastest route). In someembodiments, one or more routes of the suggested routes for Gas Vehicle1 are different routes than those shown in FIG. 6X (e.g., suggestedroute 620-8 is different from suggested route 620-7 because suggestedroute 620-7 is optionally selected to avoid the restriction whereassuggested route 620-8 is not required to avoid the restriction due tothe restriction not applying to Gas Vehicle 1). Although FIG. 6FF doesnot illustrate the inclusion of the indications that the suggestedroutes may be subject to driving restrictions (e.g., such as in FIG. 6 Xand FIG. 6CC), in some embodiments, user interface 600 includes theindications on the suggested routes and on the listings, even though GasVehicle 1 is not itself prohibited from driving in the restricted region(e.g., in the case that Gas Vehicle 1 is selected by mistake, the useris able to see that a restriction exists).

It is understood that although the description of the figures abovedescribe driving restrictions that are based on the license plate numberof a respective vehicle, the disclosure herein is not so limited. Forexamples, the features described above can be applied to drivingrestrictions based on other characteristics of vehicles, such as avehicle's VIN, a vehicle's height, width, length, weight, etc. Forexample, if a respective driving restriction prohibits vehicles withmore than two axles from traveling within a certain region or along acertain road, then device 500 can provide a process for the user toprovide information about the number of axles on the user's vehicles(e.g., in a process similar to the process to provide license plateinformation described above), and device 500 can use the providedinformation to suggest routes that that are customized for the user'svehicle (e.g., based on whether the user's vehicle is prohibited or notprohibited from driving along particular routes.

FIG. 7 is a flow diagram illustrating a method 700 of displayingcustomized navigation routes in accordance with some embodiments of thedisclosure. The method 700 is optionally performed at an electronicdevice such as device 100, device 300, and device 500 as described abovewith reference to FIGS. 1A-1B, 2-3, 4A-4B and 5A-5H. Some operations inmethod 700 are, optionally combined and/or the order of some operationsis, optionally, changed.

As described below, the method 700 displays customized navigationroutes. The method reduces the cognitive burden on a user wheninteracting with a user interface of the device of the disclosure,thereby creating a more efficient human-machine interface. Forbattery-operated electronic devices, increasing the efficiency of theuser's interaction with the user interface conserves power and increasesthe time between battery charges.

In some embodiments, an electronic device 500 in communication with adisplay generation component and one or more input devices (e.g., amobile device (e.g., a tablet, a smartphone, a media player, or awearable device), or a computer, optionally in communication with one ormore of a mouse (e.g., external), trackpad (optionally integrated orexternal), touchpad (optionally integrated or external), remote controldevice (e.g., external), another mobile device (e.g., separate from theelectronic device), a handheld device (e.g., external), and/or acontroller (e.g., external), etc.) displays (702), via the displaygeneration component, a map user interface, such as user interface 600in FIG. 6A (e.g., a user interface that displays a representation of amap of a given geographic location).

In some embodiments, the display generation component is a displayintegrated with the electronic device (optionally a touch screendisplay), external display such as a monitor, projector, television, ora hardware component (optionally integrated or external) for projectinga user interface or causing a user interface to be visible to one ormore users, etc.

In some embodiments, the user interface is a user interface of a mapapplication. In some embodiments, the map user interface is interactableby the user to view different geographic locations or change the zoomlevel of the map.

In some embodiments, while displaying the map user interface, theelectronic device receives (704), via the one or more input devices, auser input corresponding to a request to display directions from a firstlocation to a second location via a given mode of transportation, suchas user input 603 a in FIG. 6A (e.g., a request to determine one or moreroutes and/or directions from a first geographic location to a secondgeographic location).

In some embodiments, a user selects the first and/or second geographiclocation. In some embodiments, the first or second geographic locationis the determined current location of the electronic device. In someembodiments, the map user interface displays the one or more determinedroutes from the first geographic location to the second geographiclocation. In some embodiments, the one or more routes are displayed inthe map user interface. In some embodiments, the user selects the modeof transportation for which to determine the route. For example, theelectronic device is able to determine driving routes, publictransportation routes, mass transit routes, walking routes, and/orbicycling routes, etc. In some embodiments, depending on the selectedmode of transportation, the device uses different processes, algorithms,and/or restraints when determining potential routes.

In some embodiments, in response to the user input (706), in accordancewith a determination that a first vehicle is a currently selectedvehicle for which to display directions in the map user interface (e.g.,a first vehicle is selected from one or more vehicles that areregistered and/or added to the electronic device), the electronic devicedisplays (708), in the map user interface, a first suggested route fromthe first location to the second location based on a firstcharacteristic of the first vehicle, such as suggested route 620-2and/or suggested route 620-3 based on the fuel level of Gas Vehicle 1 inFIG. 6E (e.g., displaying a first proposed or suggested route from thefirst location to the second location).

In some embodiments, the first vehicle travels using the selected modeof transportation (e.g., driving on roadways). In some embodiments, thefirst vehicle is a gas vehicle, a hybrid vehicle, an electric vehicle,or any car of any fuel type (e.g., unleaded fuel, diesel, hydrogen,ethanol, self-propelled, electricity, solar energy, bio energy, etc.).

In some embodiments, the first suggested route is determined based onthe characteristics of the selected first vehicle. In some embodiments,the first characteristic is the type of fuel used by the vehicle (e.g.,gasoline, diesel, electricity, etc.). In some embodiments, the firstcharacteristic is the fuel economy of the vehicle (e.g., number of milesor kilometers a vehicle is able to travel per unit of fuel). In someembodiments, the first characteristic is the current effective range ofthe vehicle (e.g., number of miles or kilometers the vehicle iscurrently able to travel without refueling and/or recharging). In someembodiments, the first characteristic is the type of vehicle (e.g.,passenger vehicle, commercial vehicle, truck, semi-trailer truck, etc.).In some embodiments, the first characteristic is the weight of thevehicle (e.g., vehicle with a certain current gross weight). In someembodiments, the first characteristic is the size of the vehicle (e.g.,vehicle with a certain height clearance, vehicle with a certain widthclearance, etc.). In some embodiments, the first characteristic is thepower of the vehicle (e.g., horsepower, torque, etc.). In someembodiments, the first characteristic is an identifier of the vehicle(e.g., license plate number, vehicle identification number (VIN), serialnumber, etc.). In some embodiments, the first suggested route isdetermined based on the selected first vehicle's ability to traverse thepotential routes from the first location to the second location (e.g.,based on the value of the first characteristic). For example, if thefirst vehicle is an electric vehicle with a range of 100 miles and allroutes from the first location to the second location are over 100miles, then the first suggested route includes a stop to charge thebatteries (e.g., at an EV charging station) to allow the first vehicleto reach the second location. In another example, if the first vehicleis an electric vehicle with a range of 100 miles and the fastest routefrom the first location to the second location is under 100 miles, thenthe first suggested route does not include the stop to charge thebatteries. In another example, if the first vehicle is a gas vehiclewith a range of 250 miles and all routes from the first location to thesecond location are over 250 miles, then the first suggested routeincludes a stop to purchase gas (e.g., at a gas station) to fill the gastank. In another example, if the first vehicle is a semi-trailer truckwith a gross weight over a threshold amount, then the first suggestedroute automatically excludes roads and streets whose maximum weightrestrictions are below the gross weight of the vehicle. In someembodiments, if a first vehicle is not an off-road vehicle and/or is notable to traverse difficult terrain, then the first suggested routeexcludes routes that the vehicle would be unable to traverse. In someembodiments, if the first vehicle is a wide vehicle or tall vehicle,then the first suggested route excludes routes that require a narrow orlow clearance. These and other characteristics that affect a vehicle'sability to travel from one location to another are contemplated. In someembodiments, information about the first characteristic of the firstvehicle is received from a source external to the map application, asdescribed below with respect to method 900.

In some embodiments, in accordance with a determination that a secondvehicle, different from the first vehicle, is the currently selectedvehicle for which to display directions in the map user interface (e.g.,a different vehicle than the first vehicle that travels using the samemode of transportation (e.g., driving on roadways)), the electronicdevice displays (710), in the map user interface, a second suggestedroute from the first location to the second location, different from thefirst suggested route, based on a second characteristic of the secondvehicle, such as suggested route 620-4 and suggested route 620-5 basedon the current charge level of Electric Vehicle 2 in FIG. 6K (e.g.,displaying a second proposed or suggested route from the first locationto the second location for the same mode of transportation (e.g.,driving on roadways) as would be used for the suggested route for thefirst vehicle).

In some embodiments, the second vehicle is a gas vehicle, a hybridvehicle, an electric vehicle, or any car of any fuel type (e.g.,unleaded fuel, diesel, hydrogen, ethanol, self-propelled, electricity,solar energy, bio energy, etc.). In some embodiments, the secondsuggested route is determined based on the characteristics of theselected second vehicle. In some embodiments, one or morecharacteristics of the second vehicle is different from one or morecharacteristics of the first vehicle, which results in the secondsuggested route being different from the first suggested route. In someembodiments, the second suggested route takes a different route than thefirst suggested route. In some embodiments, the second suggested routeincludes more or fewer stops than the first suggested route. In someembodiments, the second characteristic of the second vehicle is the samecharacteristic type as the first vehicle, but has a different value thanthe first vehicle. For example, the first and second vehicle areoptionally both gas vehicles (e.g., same fuel type), but have differenteffective ranges (e.g., the first vehicle has enough gas to travel 100miles while the second vehicle has enough gas to travel 50 miles). Insuch embodiments, the suggested route for the first vehicle is differentfrom the suggested route for the second vehicle based on the distancebetween the first and second location and whether stops are required topurchase gas. In some embodiments, the second characteristic of thesecond vehicle is a different characteristic type than the firstcharacteristic of the first vehicle. For example, the first vehicle isoptionally a gas vehicle and the second vehicle is optionally anelectric vehicle (e.g., different fuel types), and the first suggestedroute doesn't take into account the effective range of the first vehiclewhile the second suggested route does take into account the effectiverange of the second vehicle. In such embodiments, the suggested routefor the second vehicle is optionally different from the suggested routefor the first vehicle if a stop is required to charge the second vehiclein order to reach the destination. In some embodiments, certain licenseplate patterns are restricted in a certain geography and the device isable to suggest routes based on the applicable restrictions. Forexample, some geographies may restrict travel based on whether avehicle's license plate is even or odd. In such examples, if the firstvehicle has an odd numbered license plate number (e.g., ends in an oddnumber) and the second vehicle has an even numbered license plate number(e.g., ends in an even number), then the electronic device optionallysuggests a first route for the first vehicle based on whether oddnumbered license plates are currently restricted and optionally suggestsa second, different, route for the second vehicle based on whether evennumbered license plates are currently restricted. In some embodiments,information about the second characteristic of the second vehicle isreceived from a source external to the map application, as describedbelow with respect to method 900.

The above-described manner of displaying different routes based on thecharacteristics of different vehicles for which directions are requestedquickly and efficiently provides appropriate routes to travel from afirst to a second location (e.g., by automatically taking intoconsideration the characteristic of the vehicle in suggesting routes),which simplifies the interaction between the user and the electronicdevice and enhances the operability of the electronic device and makesthe user-device interface more efficient (e.g., without requiring theuser to separately determine whether the user's vehicle is able totraverse the route unobstructed or without requiring the user tomanually edit the route to account for the vehicle's particularcharacteristics), which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiency while reducing errors inthe usage of the device.

In some embodiments, the first characteristic of the first vehicleincludes a first current estimated driving range for the first vehicle,such as in FIG. 6E (e.g., the first characteristic is an estimate of thedistance that the first vehicle is able to drive on the current fuel orcharge level). In some embodiments, the estimate of the distance thatthe first vehicle is able to drive depends on the current fuel orelectric charge level, the driving efficiency of the vehicle, the recentdriving patterns of the first vehicle, and/or the habits of the driver,etc.

In some embodiments, the first suggested route is based on the firstcurrent estimated driving range, such as in FIG. 6E (e.g., the firstsuggested route is selected based on the estimate of the distance thatthe first vehicle is able to drive on the current fuel or charge level).In some embodiments, the first suggested route includes a suggested stopto refuel or recharge the vehicle (e.g., at a gas station or electricvehicle charging station) if the first current estimated driving rangeis not enough for the first vehicle to reach the second location fromthe first location. In some embodiments, the first suggested routeincludes a suggested stop to refuel or recharge the vehicle if theestimated fuel level or battery charge level when the vehicle reachesthe destination is less than a threshold amount (e.g., such as less than5%, 10%, 15%, 20%, etc. of fuel or charge remaining, or with less than 2miles, 5 miles, 10 miles, 20 miles, 50 miles, etc. of driving rangeremaining). Thus, in some embodiments, even if the current estimatedrange of the first vehicle is enough to reach the second location fromthe first location, the device will include a suggested stop to refuelor recharge the first vehicle if the first vehicle would otherwise beleft with less than a threshold amount of fuel or electric charge. Insome embodiments, the first suggested route is selected to be less thanthe estimate of the distance that the first vehicle is able to drive(e.g., even if it is a slower route). In some embodiments, the firstsuggested route is selected to increase the driving economy of the firstvehicle (e.g., selecting routes with more steady driving, etc.) if theestimated driving range is close to the distance from the first locationto the second location, for example.

In some embodiments, the second characteristic of the second vehicleincludes a second current estimated driving range for the secondvehicle, different from the first current estimated driving range, suchas in FIG. 6K (e.g., the current estimated driving range for the secondvehicle is different from the current estimated driving range for thefirst vehicle). In some embodiments, the current estimate driving rangefor the second vehicle is different from the first vehicle because thevehicles have a different amount of fuel or charge and/or the vehicleshave different driving efficiencies (e.g., fuel or charge efficiency).

In some embodiments, the second suggested route is based on the secondcurrent estimated driving range, such as in FIG. 6K (e.g., the secondsuggested route is selected based on the estimate of the distance thatthe second vehicle is able to drive on the current fuel or chargelevel). In some embodiments, the second suggested route includes asuggested stop to refuel or recharge the vehicle (e.g., at a gas stationor electric vehicle charging station) if the second current estimateddriving range is not enough for the second vehicle to reach the secondlocation from the first location. In some embodiments, the secondsuggested route is the same route as the first suggested route (e.g.,same route optionally with the same suggested stops). In someembodiments, the second suggested route is a different route than thefirst suggested route (e.g., different route optionally with differentsuggested stops or no suggested stops).

The above-described manner of displaying different routes based on theestimated driving range of different vehicles for which directions arerequested quickly and efficiently provides appropriate routes to travelfrom a first to a second location (e.g., by automatically taking intoconsideration the driving range of the vehicle in suggesting routes),which simplifies the interaction between the user and the electronicdevice and enhances the operability of the electronic device and makesthe user-device interface more efficient (e.g., without requiring theuser to separately determine whether the user's vehicle is able to reachthe destination without running out of fuel or charge), whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiency while reducing errors in the usage of the device.

In some embodiments, in accordance with a determination that the firstcurrent estimated driving range is less than a driving distance of thefirst suggested route from the first location to the second location(e.g., the first current estimated driving range for the first vehicleis less than the distance to drive from the first location to the secondlocation (e.g., the distance of the fastest route, the distance of theshortest route, etc., optionally by a threshold amount such as 0 miles,2 miles, 5 miles, 10 miles, 20 miles, 50 miles, or the equivalent of 5%,10%, 15%, 20%, 25%, etc. of fuel or charge remaining)), the firstsuggested route includes a suggested stop for increasing a remainingdriving range of the first vehicle, such as suggested stop 632-1 in FIG.6E (e.g., the first suggested route is selected based on the estimate ofthe distance that the first vehicle is able to drive on the current fuelor charge level).

In some embodiments, the first suggested route includes a suggested stopto refuel or recharge the first vehicle (e.g., at a gas station orelectric vehicle charging station). In some embodiments, the firstsuggested route includes a plurality of suggested stops to refuel orrecharge the first vehicle if multiple stops to refuel or recharge arerequired to reach the second location from the first location. In someembodiments, if the second current estimated driving range for thesecond vehicle is less than the distance to drive from the firstlocation to the second location, then the second suggested routeincludes a suggested stop to refuel or recharge the second vehicle. Insome embodiments, the suggested stop for the second vehicle is differentfrom the suggested stop for the first vehicle based on the difference inthe characteristics of the two vehicles (e.g., different fuel types,different driving range, etc.). In some embodiments, the secondsuggested route for the second vehicle does not include a suggestedstop.

The above-described manner of including a suggested stop in thesuggested routes quickly and efficiently provides appropriate routes totravel from a first to a second location (e.g., by automatically takinginto consideration whether the vehicle should be refueled or rechargedalong the way in order to reach the destination), which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient (e.g., without requiring the user to separately determinewhether the user's vehicle is able to reach the destination and thenmanually searching for and adding a refueling or recharging stop to theroute), which additionally reduces power usage and improves battery lifeof the electronic device by enabling the user to use the electronicdevice more quickly and efficiency while reducing errors in the usage ofthe device.

In some embodiments, in accordance with a determination that the firstvehicle is associated with a first charging network (e.g., the firstvehicle (optionally the driver of the first vehicle) has a subscription,agreement, or relationship with a network of charging stations, chargingstation company, and/or gas station company, the driver of the firstvehicle has a preferred network of charging stations, charging stationcompany, and/or gas station company and/or the first vehicle isrestricted to a particular network of charging stations (e.g.,optionally due to limitations of the first vehicle, such as thecompatible car types)), the suggested stop for increasing the remainingdriving range of the first vehicle is a first stop associated with thefirst charging network, such as in FIG. 6L (e.g., the suggested stop iswithin the network of charging stations, is a charging station of thecharging station company, or is a gas station of the gas station companythat the user has a relationship with or prefers).

In some embodiments, the first vehicle's association with a particularcharging network is set by a user or provided by a third-partyapplication or server as described below with respect to method 900.Thus, in some embodiments, device 500 is able to determine the chargingstations and/or gas stations within the user's network (e.g., networkthat the user or vehicle is associated with, a preferred network, orrequired network for the first network) and suggest those particularstations. In some embodiments, determining the charging station and/orgas station within the user's network includes receiving information forthe charging network and/or gas station from a source external to themap application, as discussed below with respect to method 900. In someembodiments, in accordance with a determination that the first vehicleis associated with a second charging network, different from the firstcharging network, the suggested stop is a second stop, different fromthe first stop, associated with the second charging network.

The above-described manner of displaying suggested stops that are withina particular charging network quickly and efficiently providesappropriate recharging stops along the route from a first to a secondlocation (e.g., by automatically taking into consideration the chargingnetwork that is preferred by the user or otherwise associated with thevehicle when determining the recharging stops to add to the suggestedroute), which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient (e.g., withoutrequiring the user to separately determine whether the suggestedrecharging stop is within the user's charging network), whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiency while reducing errors in the usage of the device.

In some embodiments, the first characteristic of the first vehicleincludes a first current estimated driving range for the first vehicle,such as in FIG. 6E (e.g., the first characteristic is an estimate of thedistance that the first vehicle is able to drive on the current fuel orcharge level). In some embodiments, the estimate of the distance thatthe first vehicle is able to drive depends on the current fuel orelectric charge level, the driving efficiency of the vehicle, the recentdriving patterns of the first vehicle, and/or the habits of the driver,etc.

In some embodiments, the first suggested route is based on the firstcurrent estimated driving range, such as in FIG. 6E (e.g., the firstsuggested route is selected based on the estimate of the distance thatthe first vehicle is able to drive on the current fuel or charge level).In some embodiments, the first suggested route includes a suggested stopto refuel or recharge the vehicle (e.g., at a gas station or electricvehicle charging station) if the first current estimated driving rangeis not enough for the first vehicle to reach the second location fromthe first location.

In some embodiments, in response to the user input, in accordance with adetermination that a third vehicle (e.g., a no vehicle option) iscurrently selected for which to display directions in the map userinterface, the electronic device displays, in the map user interface, athird suggested route from the first location to the second location,that is not based on a current estimated driving range for a vehicle,such as suggested route 620-1 and suggested route 620-2 in FIG. 6B whenno vehicle is selected (e.g., no vehicle has been selected for which toprovide customized routes).

In some embodiments, the map application includes a list of vehiclesthat have been registered with the map application from which the useris able to select a car to determine directions from. In someembodiments, the list of vehicles includes an “other vehicle” option (oroptionally an option to disable customized routes) that is notassociated with a particular, the selection of which causes the deviceto provide generic routes (e.g., not customized to a particular vehicle,and without regard to the characteristics of a particular vehicle). Insome embodiments, if the user selects the “other vehicle” option todisable customized routes that are based on the characteristics of aparticular vehicle or if the user otherwise disabled customized routes(e.g., via a setting), then customized estimated driving ranges are notavailable. Thus, if no particular vehicle is selected or if customizedroutes are disabled, then current estimated driving range information isunavailable (e.g., because it is not associated with a specificvehicle), and the third suggested route is selected without regard tothe driving range of a particular vehicle (e.g., without regard to thecurrent estimated driving range of the first vehicle or the currentestimated driving range of the second vehicle). In some embodiments, thethird suggested route does not automatically include any refueling orrecharging stops. In some embodiments, the third suggested route is thefastest route from the first location to the second location. In someembodiments, the third suggested route is the shortest route from thefirst location to the second location. In some embodiments, the thirdsuggested route is the same as the first suggested route and/or thesecond suggested route (e.g., if the first current estimated drivingrange is more than enough to reach the second location from the firstlocation). In some embodiments, the third suggested route is differentthan the first suggested route and/or the second suggested route (e.g.,if the first current estimated driving range is not enough to reach thesecond location from the first location). In some embodiments, ifcurrent driving range information is not available for the secondvehicle (e.g., because the map application is unable to communicate withthe external source that is providing the information), then the secondsuggested route is selected without regard to the driving range for thesecond vehicle (e.g., similar to the third suggested route describedherein for generic vehicles), optionally with an indication that thesuggested route is not customized for the second vehicle.

The above-described manner of displaying a route based on thecharacteristics of a vehicle or a generic route if no vehicle isselected quickly and efficiently provides the option to choose between acustomized route or a generic route (e.g., by providing a customizedroute if car information is available but otherwise providing a generalroute if car information is not available), which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient (e.g., without requiring the user to always select aspecific vehicle or requiring the user to add vehicles to theapplication before requesting directions), which additionally reducespower usage and improves battery life of the electronic device byenabling the user to use the electronic device more quickly andefficiency while reducing errors in the usage of the device.

In some embodiments, displaying the first suggested route from the firstlocation to the second location includes displaying an estimated totaltravel time for the first suggested route, such as the indication of 59minutes and 1 hour 4 minutes in FIG. 6E (e.g., the first suggested routeis displayed with an indication of an estimated amount of time to travelalong the first suggested route to reach the second location from thefirst location).

In some embodiments, in accordance with a determination that the firstsuggested route includes a suggested stop for increasing a remainingdriving range of the first vehicle, the estimated total travel timeincludes an estimated time to increase the remaining driving range ofthe first vehicle at the suggested stop, such as in FIG. 6E (e.g., ifthe first suggested route includes a suggested stop to refuel orrecharge the vehicle, then the displayed estimated amount of time totravel includes an estimated amount of time required to refuel orrecharge the vehicle). For example, if the amount of time it takes torecharge the vehicle to a respective suggested amount is estimated totake 15 minutes, then the estimated total travel time includes the 15minutes of charge time. In some embodiments, if the second suggestedroute (e.g., for the second vehicle) includes a suggested stop to refuelor recharge the second vehicle, then the estimated total travel timeincludes the estimated time for refueling or recharging.

The above-described manner of displaying estimated travel time thatincludes time to refuel and/or recharge provides a more accurateestimate of the amount of time required to reach the destination (e.g.,by automatically taking into consideration the amount of time requiredto refuel or recharge the vehicle at a suggested refueling or rechargingstop), which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient (e.g., withoutrequiring the user to separately determine how long the refueling orrecharging will take and adding that to the estimated duration orestimated time of arrival), which additionally reduces power usage andimproves battery life of the electronic device by enabling the user touse the electronic device more quickly and efficiency while reducingerrors in the usage of the device.

In some embodiments, the electronic device displays, via the displaygeneration component, one or more representations of one or moresegments associated with the first suggested route, such as in FIG. 6F(e.g., while displaying the step-by-step directions of the firstsuggested route on a user interface (e.g., optionally in response to auser input selecting the first suggested route or a user inputrequesting display of the step-by-step directions of the first suggestedroute)), wherein a respective representation of a respective segmentincludes an indication of an estimated state of the first characteristicof the first vehicle during the respective segment, such as indication638-1, indication 638-2, and indication 638-3 in FIG. 6F (e.g., some orall of the step-by-step directions of the first suggested route aredisplayed with an indication of the estimated amount of fuel or chargelevel of the respective vehicle when the respective vehicles reaches therespective step-by-step direction or while the vehicle is following therespective step-by-step direction).

In some embodiments, the estimated fuel or charge level are displayedfor steps that the first vehicle has not already followed (e.g., forfuture steps). In some embodiments, estimated fuel or charge level arenot displayed for steps that the first vehicle has already performed. Insome embodiments, the actual fuel or charge level are displayed forsteps that the first vehicle has already performed. For example, the“start” step (e.g., first step) and/or the “arrive” step (e.g., finalstep) include an indication of the estimated charge level for when thevehicle begins traveling along the suggested route and the estimatedcharge level for when the vehicle arrives at the destination,respectively. In some embodiments, if the first suggested route includesa suggested stop to recharge or refuel the vehicle, then the suggestedstop includes an indication of the estimated fuel or charge level forwhen the vehicle arrives at the suggested stop. In some embodiments, theestimated fuel or charge level can be displayed for other steps. In someembodiments, the estimated fuel or charge level is the estimated fuel orcharge level for when the user arrives at the beginning of the step,when the user completes the step, or any time while the first vehicle isfollowing the step (e.g., along the route corresponding to the step). Insome embodiments, the estimated charge or fuel level updates while thefirst vehicle is traveling along the suggested route based on new orupdated information for the current charge or fuel levels of the firstvehicle.

The above-described manner of displaying estimates of the fuel or chargelevel at respective steps of the suggested route provides the user withinformation about the fuel or charge level, which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient (e.g., allowing a user to determine, using the providedestimates, whether to select the suggested route, select another route,or modify the suggested route), which additionally reduces power usageand improves battery life of the electronic device by enabling the userto use the electronic device more quickly and efficiency while reducingerrors in the usage of the device.

In some embodiments, while the first vehicle is the currently selectedvehicle and while displaying the first suggested route from the firstlocation to the second location, the electronic device receives, via theone or more input devices, a user input corresponding to a request toselect the second vehicle as the currently selected vehicle, such as inFIG. 6I (e.g., while displaying the suggested route(s) for the firstvehicle, receive an input switching to the second vehicle).

In some embodiments, while displaying the first suggested route, othersuggested routes are optionally also displayed. In some embodiments, thefirst suggested route is the recommended route and the other suggestedroutes are alternative routes and are optionally displayed de-emphasizedas compared to the first suggested route (e.g., a dimmer color, adifferent color, with an indication that it is not the most recommendedroute, that it is an alternative route, etc.). In some embodiments, thesecond suggested route (e.g., that would be displayed for the secondvehicle were it selected) is one of the other suggested routes that aredisplayed.

In some embodiments, in response to receiving the user inputcorresponding to the request to select the second vehicle as thecurrently selected vehicle, the electronic device displays, in the mapuser interface, the second suggested route, such as in FIG. 6J (e.g.,switching from displaying the first suggested route to displaying thesecond suggested route).

In some embodiments, the second suggested route is displayed because thesecond suggested route is the recommended route for the second vehiclebased on the characteristic of the second vehicle. In some embodiments,the first suggested route is ceased to be displayed. In someembodiments, the first suggested route remains displayed but isdisplayed with an indication that it is not the most recommended route(e.g., displayed with a text that indicates that the first suggestedroute is an alternative route, or displayed with a de-emphasized coloras compared to the second suggested route and/or as compared to thecolor of the first suggested route before receiving the input, etc.). Insome embodiments, when the input was received, the second suggestedroute was displayed concurrently with the first suggested route, but wasdisplayed with an indication that it was not the most recommended route,and in response to the user input, the second suggested route is updatedto indicate that the second suggested route is now the most recommendedroute (e.g., not displayed with a text that indicates that the secondsuggested route is an alternative route, not displayed with ade-emphasized color, displayed with a text that indicates that it is thefastest route, displayed with an emphasized color, etc.).

The above-described manner of switching from suggesting a first route tosuggesting a second route when the user switches from selecting thefirst vehicle to selecting the second vehicle (e.g., by automaticallytaking into consideration the characteristics of the second vehicle andswitching to suggesting routes based on the characteristics of thesecond vehicle rather than the routes based on the characteristics ofthe first vehicle), which simplifies the interaction between the userand the electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient (e.g., withoutrequiring the user to clear the search results and perform the queryagain in order to view routes that are customized for the secondvehicle), which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiency while reducing errors in the usage ofthe device.

In some embodiments, while navigating along the first suggested route(e.g., while the device is in a navigation mode associated with thefirst suggested route in while turn-by-turn navigation instructions areprovided to the user), the electronic device determines that the devicehas arrived at a suggested stop for increasing a remaining driving rangeof the first vehicle, such as in FIG. 6P (e.g., the device and/or thefirst vehicle has reached the location of the suggested stop and/or hasreached within a threshold distance of the location of the suggestedstop (e.g., within 30 feet, 50 feet, 200 feet, 500 feet, 2000 feet,etc.)). In some embodiments, the first vehicle is an electric vehicleand the suggested stop is a charging station for charging the electricvehicle.

In some embodiments, in response to determining that the device hasarrived at the suggested stop for increasing the remaining driving rangeof the first vehicle, in accordance with a determination that anaccessory of a first type is required to increase the remaining drivingrange of the first vehicle, the electronic device displays, via thedisplay generation component, an indication of the accessory of thefirst type, such as instruction 644 in FIG. 6P (e.g., displaying anindication of the type of adapter required to charge the first vehicleat the charging station associated with the suggested stop).

For example, the charging station at the suggested stop is configuredwith one or more different outlet or plug types that are compatible withone or more charger plugs. In some embodiments, if an accessory of asecond type (e.g., a second type of adapter) is required to use thecharging station, then an indication of the accessory of the second typeis displayed. In some embodiments, if the first vehicle is equipped witha compatible charger plug, then the first vehicle is able to use thecharging station without using an adapter and thus an indication of anadapter is not displayed. In some embodiments, if the first vehicle isnot equipped with a compatible charger plug, but an adapter is availableto convert the incompatible charger plug to a compatible charger plug,then an indication of the adapter is displayed, thus indicating theadapter required to use the charging station. In some embodiments, thedevice provides only adapters that the user has previously indicatedthat the user is in possession of.

The above-described manner of displaying an accessory required to usethe charging station quickly and efficiently provides the user withinformation of how to connect to the charging station (e.g., byautomatically taking into consideration the requirements of the chargingstation, the type of plug installed on the vehicle, and the adaptersthat are available), which simplifies the interaction between the userand the electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient (e.g., withoutrequiring the user to separately determine whether an adapter isrequired or whether the user's vehicle is actually able to use thecharging station), which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiency while reducing errors inthe usage of the device.

In some embodiments, while navigating along the first suggested route,the electronic device determines that the device has arrived at asuggested stop for increasing a remaining driving range for the firstvehicle, such as in FIG. 6P (e.g., the device and/or the first vehiclehas reached the location of the suggested stop and/or has reached withina threshold distance of the location of the suggested stop (e.g., within30 feet, 50 feet, 200 feet, 500 feet, 2000 feet, etc.)).

In some embodiments, in response to determining that the device hasarrived at the suggested stop for increasing the effective range of thefirst vehicle, the electronic device displays, via the displaygeneration component, a first affordance to pause the navigation alongthe first suggested route, such as button 662 in FIG. 6Q (e.g.,displaying a button to pause navigation mode).

In some embodiments, while displaying the first affordance to pause thenavigation, the electronic device receives, via the one or more inputdevices, a user input selecting the first affordance, such as in FIG. 6Q(e.g., a tap input on the button).

In some embodiments, in response to receiving the user input selectingthe first affordance, the electronic device displays, via the displaygeneration component, a second affordance to resume navigating along thefirst suggested route (e.g., displaying a button to resume navigationmode) and an indication of the first characteristic of the first vehiclewhile it is increasing, such as notification 668 in FIG. 6R orindication 672 in FIG. 6T (e.g., display the current charge level, thecurrent estimated driving range, and/or the amount of time remaining torecharge the first vehicle in order to reach the suggested chargelevel).

In some embodiments, the button to resume navigation mode replaces thebutton to pause navigation mode. In some embodiments, the button topause navigation mode becomes the button to resume navigation mode. Insome embodiments, a selectable option is displayed on the map userinterface for resuming navigating along the first suggested while notdisplaying any directions or routes. In some embodiments, the devicedisplays a notification that is selectable to display the mapsapplication and optionally resume navigating along the first suggestedroute.

In some embodiments, the indication dynamically updates as updatedinformation about the first characteristic is received. In someembodiments, the maps application continuously (e.g., at a predeterminedfrequency, such as once every 0.25 seconds, 0.5 seconds, 1 second, 3seconds, 5 seconds, etc.) polls a third party application or source(e.g., as described below with respect to method 900) to receive updatedinformation for the first characteristic.

The above-described manner of monitoring the first characteristic as thefirst vehicle is refueling or recharging quickly and efficientlyprovides the user with updates on the status of the refueling orrecharging (e.g., by automatically displaying updated fuel and chargeinformation even if the user has paused active navigation), whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., without requiring the userto navigate to a separate user interface to determine to view thecurrent status of the fuel or charge level), which additionally reducespower usage and improves battery life of the electronic device byenabling the user to use the electronic device more quickly andefficiency while reducing errors in the usage of the device.

In some embodiments, while navigating along the first suggested route,the electronic device determines that a current estimated driving rangefor the first vehicle is less than a remaining driving distance of thefirst suggested route from a current location to the second location,such as in FIG. 6V (e.g., while in navigation mode and traveling alongthe first suggested route, receiving updated information about the firstvehicle and determining based on the updated information that the firstvehicle will not reach the destination from the first vehicle's currentlocation).

In some embodiments, the received updated information is an updatedestimated driving range or an updated current charge or fuel level. Forexample, if the first vehicle did not charge or refuel to the suggestedlevel at a previous suggested stop, or if the first vehicle took adifferent route than the suggested route, then the estimated drivingrange may not be enough for the first vehicle to reach the destinationand the device will suggest a stop to refuel or recharge the firstvehicle. In some embodiments, the updated information is received from asource external to the map application, such as described below withrespect to method 900.

In some embodiments, in response to determining that the currentestimated driving range for the first vehicle is less than the remainingdriving distance of the first suggested route from the current locationto the second location, the electronic device updates the firstsuggested route to include a suggested stop for increasing a remainingdriving range of the first vehicle, such as in FIG. 6V (e.g., if theupdated estimated driving range suggests that the first vehicle does nothave enough fuel or electric charge to reach the destination (or willreach the destination with less than a threshold amount of fuel orcharge, such as less than 5%, 10%, 15%, 20%, etc. of fuel or chargeremaining, or with less than 2 miles, 5 miles, 10 miles, 20 miles, 50miles, etc. of driving range remaining), then add a suggested stop tothe route to refuel or recharge the first vehicle).

Thus, in some embodiments, the device is able to dynamically addsuggested stops to refuel or recharge while in navigation mode or whilethe vehicle is traveling towards the destination, without requiring theuser to perform another query to route from the vehicle's currentposition to the destination to determine where to refuel or recharge thevehicle.

The above-described manner of suggesting a stop to refuel or rechargethe vehicle while navigating along a route quickly and efficientlyprovides the user with a suggested stop if a stop is now required toreach the destination (e.g., by automatically determining that theestimated driving range is such that the first vehicle will not be ableto reach the destination and suggesting a stop to refuel or recharge),which simplifies the interaction between the user and the electronicdevice and enhances the operability of the electronic device and makesthe user-device interface more efficient (e.g., without requiring theuser to separately monitor the fuel or charge level and separatelydetermine whether the vehicle will reach the destination and thenmanually add a refueling or recharging stop to the route), whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiency while reducing errors in the usage of the device.

In some embodiments, the first characteristic of the first vehicle isassociated with a first driving restriction for the first vehicle, suchas in FIG. 6CC (e.g., a geographic region (e.g., city, county, area,etc.) has implemented driving restrictions that apply certain sets ofvehicles based on the characteristics of the respective vehicle). Insome embodiments, driving restrictions may be implemented based on thelicense plate of the vehicles. For example, during certain periods oftime, odd numbered vehicles (e.g., vehicles with license plates endingin an odd number) are not permitted to drive in the restricted region,but even numbered vehicles (e.g., vehicles with license plates ending inan even number) are permitted to drive in the restricted region. In someembodiments, restrictions based on other characters are possible, suchas the type of vehicle (e.g., whether the vehicle is a passengervehicle, commercial vehicle, truck, SUV, semi-tractor trailer truck,whether the vehicle is taller than a certain height, whether the vehicleis above a certain gross weight, etc.).

In some embodiments, the first suggested route is based on the firstdriving restriction, such as in FIG. 6CC (e.g., the route suggested isbased on whether the first vehicle is subject to the drivingrestriction). For example, if the driving restriction is that evennumbered cars are not permitted to drive in a restricted region and thenormally suggested route (e.g., the fastest route) would route thevehicle through the restricted region, then instead of suggesting thenormally suggested route, a route that avoids the restriction (e.g.,routes around the restricted region) is suggested to the user. In someembodiments, the normally suggested route is also concurrently displayedto the user, but displayed with an indication that it is affected by therestriction. In some embodiments, if the restriction only applies duringa particular time window, the suggested route is only affected duringthose time windows (e.g., if the current time is outside the time windowin which the restriction applies, then the suggested route is selectedwithout regard to the restriction.

In some embodiments, the second characteristic of the second vehicle isassociated with a second driving restriction for the second vehicle,different from the first driving restriction, such as in FIG. 6FF (e.g.,the second vehicle has a different characteristic from the first vehicleand thus is either also restricted from driving in the restricted regionor is not restricted from driving in the restricted region).

In some embodiments, the second suggested route is based on the seconddriving restriction, such as in FIG. 6FF (the suggested route for thesecond vehicle is based on whether the second vehicle is affected by thedriving restriction).

In some embodiments, the driving restriction that applies to the secondvehicle is the same driving restriction than the one that applies to thefirst vehicle and the device is able to determine whether the firstvehicle or the second vehicle is prohibited from traveling a particularroute due to that driving restriction. In some embodiments, the drivingrestrictions that applies to the second vehicle is a different drivingrestriction than the one that applies to the first vehicle and thedevice is able to determine whether the second vehicle is able to travela particular route based on the driving restriction that affects thesecond vehicle. In some embodiments, the suggested route for the secondvehicle is the same as the suggested route for the first vehicle becausethe second vehicle and the first vehicle are similarly affected by thedriving restriction (e.g., are both even numbered cars). In someembodiments, the suggested route for the second vehicle is differentfrom the suggested route for the first vehicle because the vehicles areaffected differently by the restriction. In some embodiments, if thesecond vehicle is not affected by the restriction (e.g., is permitted totravel in the restricted zone), then the suggested route is selectedwithout regard to the restriction (e.g., is the fastest route, and/orshortest route, etc.). In some embodiments, the second vehicle isaffected by the same restriction as the restriction that affects thefirst vehicle and also an additional restriction, different from therestriction that affects the first vehicle, and the suggested route isselected to avoid both restrictions. In some embodiments, whether a caris affected by a restriction is based on the characteristics of thevehicle, such as the license plate pattern or the vehicle type. In someembodiments, a different set of restrictions apply to different types ofvehicles (e.g., a first set of restrictions apply to passenger vehiclesand a second set of restrictions apply to commercial vehicles, etc.). Insome embodiments, the maps application receives information about thecharacteristics of the vehicle from a source external to the mapapplication, as described below with respect to method 900. In someembodiments, a user provides the map application with license plateinformation, similarly to the process to add a vehicle to the maps appas described below with respect to method 900.

The above-described manner of displaying different routes based onwhether a respective vehicle is affected by a driving restrictionquickly and efficiently provides appropriate routes to travel from afirst to a second location (e.g., by automatically taking intoconsideration the restrictions that apply to the respective vehicle),which simplifies the interaction between the user and the electronicdevice and enhances the operability of the electronic device and makesthe user-device interface more efficient (e.g., without requiring theuser to separately determine whether the user's vehicle is prohibited todrive in a restricted region), which additionally reduces power usageand improves battery life of the electronic device by enabling the userto use the electronic device more quickly and efficiency while reducingerrors in the usage of the device.

In some embodiments, the first driving restriction is determined usingan anonymized characteristic corresponding to the first characteristicof the first vehicle (e.g., anonymize the characteristic of the vehiclewhen determining the suggested route for the vehicle).

In some embodiments, a third party server or third party service is usedto gather travel information or road conditions. For example, a serverhosted by a government agency provides current traffic information,current outages, viable routes, and/or restriction information. In someembodiments, a server maintains driving restriction information and isable to be queried to determine whether a particular vehicle isprohibited from driving in a restricted zone. In some embodiments, theserver is queried by providing the vehicle's license plate informationand the intended route and the server provides a determination onwhether the vehicle is prohibited from driving along a part of or all ofthe intended route. In some embodiments, because the driving restrictionis based on a pattern of the license plate (e.g., whether it ends in aneven or odd number) rather than the full license plate number, thedevice is able to anonymize the license plate to preserve the privacy ofthe user and thus prevent information about the user's travel habits orhistory from being sent away from the device and/or to another entity.For example, the device provides, to the server, a randomly generatedlicense plate number (that optionally follows the license plate patternof the region), that ends with a randomly generated even or odd number(whichever is the case based on whether the first vehicle is an even orodd number) to simulate the license plate pattern of the first vehiclewhile not providing the actual license plate information of the firstvehicle. Thus, in some embodiments, the device uses an anonymizedcharacteristic that is the same type of characteristic as the firstcharacteristic (e.g., optionally the characteristic that is relevant tothe respective driving restriction.

The above-described manner of determining suggested routes using ananonymized characteristic of the vehicle quickly and efficientlydetermines the appropriate routes for the respective vehicle whilemaintaining the privacy of the user (e.g., by automatically removingidentifying information when determining the routes to suggest), whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., by allowing the user toenter the vehicle's true details and without requiring the user toprovide incorrect identifying information, which may result in incorrectdetermination of whether the user's vehicle is restricted, for example,if the restriction is changed), which additionally reduces power usageand improves battery life of the electronic device by enabling the userto use the electronic device more quickly and efficiency while reducingerrors in the usage of the device.

In some embodiments, the first characteristic of the first vehicle isassociated with a first driving restriction for the first vehicle, suchas in FIG. 6CC (e.g., the first characteristic of the first vehicle isrelevant to a driving restriction for a restricted region and the firstvehicle is either prohibited or not prohibited from traveling in therestricted region). In some embodiments, the license plate pattern ofthe first vehicle matches the restriction pattern such that the firstvehicle is restricted or not restricted.

In some embodiments, the first suggested route is based on the firstdriving restriction, such as in FIG. 6CC (e.g., the first suggestedroute provided to the user is selected for the first vehicle based onwhether the first vehicle is prohibited or not prohibited from drivingin the restricted region). In some embodiments, if the first vehicle isprohibited, the first suggested route is a route that avoids therestriction (e.g., goes around the restricted region). In someembodiments, if the first vehicle is not prohibited, the first suggestedroute is selected without regard to the restriction (e.g., is thefastest route or shortest route, etc.).

In some embodiments, in response to the user input, in accordance with adetermination that no vehicle is currently selected for which to displaydirections in the map user interface, the electronic device displays, inthe map user interface, a third suggested route from the first locationto the second location, that is not based on a driving restriction, suchas in FIG. 6X (e.g., no vehicle has been selected for which to providecustomized routes).

In some embodiments, the map application includes a list of vehiclesthat have been registered with the map application from which the useris able to select a car to determine directions from. In someembodiments, the list of vehicles includes an “other vehicle” option (oroptionally an option to disable customized routes) that is notassociated with a particular, the selection of which causes the deviceto provide generic routes (e.g., not customized to a particular vehicle,and without regard to the characteristics of a particular vehicle). Insome embodiments, if the user selects the “other vehicle” option todisable customized routes that are based on the characteristics of aparticular vehicle or if the user otherwise disabled customized routes(e.g., via a setting), then customized estimated driving ranges are notavailable. Thus, if no particular vehicle is selected or if customizedroutes are disabled, then license plate information is unavailable(e.g., because it is not associated with a specific vehicle), and thethird suggested route is selected without regard to the drivingrestrictions of a particular vehicle (e.g., without regard to thedriving restrictions of the first vehicle or the driving restrictions ofthe second vehicle). In some embodiments, the third suggested routetravels through the restricted region. In some embodiments, the thirdsuggested route is the fastest route from the first location to thesecond location. In some embodiments, the third suggested route is theshortest route from the first location to the second location. In someembodiments, the third suggested route is the same as the firstsuggested route and/or the second suggested route (e.g., if the firstvehicle is not prohibited from traveling in the restricted region). Insome embodiments, the third suggested route is different than the firstsuggested route and/or the second suggested route (e.g., if the firstvehicle and/or the second vehicle are prohibited from traveling in therestricted region). In some embodiments, if driving restrictioninformation is not available for the second vehicle (e.g., because themap application is unable to communicate with the external source thatis providing the information), then the second suggested route isselected without regard to the driving restrictions that may apply tothe second vehicle (e.g., similar to the third suggested route describedherein for generic vehicles, optionally with an indication that thesuggested route is not customized for the second vehicle).

The above-described manner of displaying a route based on whether aparticular vehicle is restricted or a generic route that is not based onwhether a particular vehicle is restricted quickly and efficientlyprovides the option to choose between a customized route or a genericroute (e.g., by providing a customized route if car information isavailable but otherwise providing a general route if car information isnot available), which simplifies the interaction between the user andthe electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient (e.g., withoutrequiring the user to always select a specific vehicle or requiring theuser to add vehicles to the application before requesting directions),which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiency while reducing errors in the usage of the device.

In some embodiments, in accordance with a determination that the thirdsuggested route passes through an area restricted by a respectivedriving restriction, the electronic device displays, via the displaygeneration component, an indication that the third suggested routepasses through the area restricted by a driving restriction, such as inFIG. 6X (e.g., if no vehicle is selected, then the suggested route thatis displayed without regard to whether a specific vehicle is affected bya restricted region).

In some embodiments, if the third suggested route passes through arestricted region or would otherwise be affected by the restrictedregion, then display an indication that the suggested route is affectedby the restricted region to notify the user that a restriction may applyto the user's vehicle. In some embodiments, the indication is a textindicator that a restriction applies. In some embodiments, theindication is an icon indicating that a restriction applies. In someembodiments, the icon is displayed at or near the position of theportion of the suggested route that enters into the restriction region.In some embodiments, the icon is displayed on a respective listing of asuggested route in the list of suggested routes (which are optionallydisplayed in response to a request for directions) to indicate that thesuggested route is affected by a driving restriction. In someembodiments, the indication identifies the type of restriction and/orindicates how or why the indication applies to certain vehicles (e.g.,the indication includes a textual description of the restriction and/orthe icon represents the type of restriction).).

The above-described manner of displaying an indication if a route isaffected by a driving restriction (e.g., when the route is a genericroute that is not customized for a particular vehicle) quickly andefficiently provides the user with an indication that the user's vehiclemay be subject to the driving restriction (e.g., by displaying theindication that a driving restriction applies when the user has notselected a specific vehicle to search routes for), which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient (e.g., without requiring the user to always select aspecific vehicle or requiring the user to add vehicles to theapplication before requesting directions to receive information aboutdriving restrictions), which additionally reduces power usage andimproves battery life of the electronic device by enabling the user touse the electronic device more quickly and efficiency while reducingerrors in the usage of the device.

In some embodiments, in accordance with a determination that a givenroute from the first location to the second location is associated witha driving restriction (e.g., if a suggested route travels through arestricted region and is thus affected by a driving restriction), inaccordance with a determination that one or more criteria are satisfied(e.g., no cars have yet been added to the map application), theelectronic device displays, via the display generation component, anaffordance for adding information about a respective vehicle to the mapuser interface, such as button 688 in FIG. 6 W (e.g., display anotification, an element on the user interface, and/or a link or buttonthat is selectable to initiate a process to add vehicle information tothe map application).

In some embodiments, a notification is displayed on a lock screen, awake screen, or on the notification user interface indicating thatlicense plate information can be added to the map application. In someembodiments, a banner or other user interface element is displayed inthe map application indicating that license plate information can beadded to the map application. In some embodiments, if the one or morecriteria are not satisfied, the affordance for adding information aboutthe respective vehicle is not displayed.

In some embodiments, the electronic device receives, via the one or moreinput devices, a user input selecting the affordance (e.g., a tap inputor any other selection input on the affordance). In some embodiments, inresponse to receiving the user input, the electronic device initiates aprocess to add the information about the respective vehicle to the mapuser interface (e.g., initiate a process for the user to add licenseplate information to the maps application (e.g., information associatedwith the driving restriction)).

In some embodiments, the process includes displaying a wizard orstep-by-step instructions to guide the user through adding license plateinformation. In some embodiments, the maps application maintains a listof vehicles associated with the user, which optionally includes licenseplate information and/or other characteristics for the respectivevehicles. In some embodiments, the characteristics of the vehicles areautomatically populated with information received from an externalsource, as discussed below with respect to method 900.

The above-described manner of adding vehicle information (e.g.,providing an affordance that is selectable to initiate a process to addvehicle information to the map application) quickly and efficientlyprovides the user with the ability to provide the map application withvehicle information that is relevant to a driving restriction, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient, which additionally reduces powerusage and improves battery life of the electronic device by enabling theuser to use the electronic device more quickly and efficiency whilereducing errors in the usage of the device.

In some embodiments, while navigating along the first suggested route,the electronic device determines that a current location of the devicesatisfies one or more criteria associated with a driving restriction ofthe first suggested route, such as in FIG. 6DD (e.g., while innavigation mode and traveling along the suggested route, determiningthat the user is about to enter into a restricted region (optionallyonly if the currently selected vehicle is prohibited from traveling inthe restricted region or if no vehicle is currently selected)).

In some embodiments, the suggested route includes directions that guidesthe user into a restricted region. In some embodiments, the suggestedroute that the user is traveling along is provided because the user hasnot selected a particular car to provide routes for or because the userchose to navigate using a route that travels into the restricted region.

In some embodiments, in response to determining that the currentdirection satisfies the one or more criteria associated with the drivingrestriction, the electronic device displays, via the display generationcomponent, an indication of the driving restriction, such as in FIG. 6DD(e.g., within a threshold distance of entering into the restrictedregion (e.g., 10 feet, 50 feet, 100 feet, 300 feet, 500 feet, 1000 feet,etc.), displaying an indication that the user is about to enter therestricted region).

In some embodiments, the indication is a textual indication that arestricted region is upcoming. In some embodiments, the indication is anicon in the user interface at or near the location corresponding to therestricted region. In some embodiments, the indication identifies thetype of restriction and/or indicates how or why the indication appliesto certain vehicles (e.g., the indication includes a textual descriptionof the restriction and/or the icon represents the type of restriction).

The above-described manner of displaying an indication that a user isabout to enter a restricted region quickly and efficiently provides theuser with a visual indication that the user may be prohibited fromtraveling in the restricted region, which simplifies the interactionbetween the user and the electronic device and enhances the operabilityof the electronic device and makes the user-device interface moreefficient (e.g., without requiring the user to separately determinewhere the boundaries of the restricted region are and whether arestriction applies to the user's current selected vehicle), whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiency while reducing errors in the usage of the device.

It should be understood that the particular order in which theoperations in FIG. 7 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 900 and 1100) are also applicable in an analogous manner tomethod 700 described above with respect to FIG. 7 . For example, theoperation of the electronic device of displaying customized navigationroutes described above with reference to method 700 optionally has oneor more of the characteristics of receiving information aboutcharacteristics of respective vehicles, anonymizing a vehicleidentifier, etc., described herein with reference to other methodsdescribed herein (e.g., methods 900 and 1100). For brevity, thesedetails are not repeated here.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., as described with respect to FIGS. 1A-1B, 3, 5A-5B) orapplication specific chips. Further, the operations described above withreference to FIG. 7 are, optionally, implemented by components depictedin FIGS. 1A-1B. For example, displaying operations 702, 708, and 710 andreceiving operation 704 are, optionally, implemented by event sorter170, event recognizer 180, and event handler 190. Event monitor 171 inevent sorter 170 detects a contact on touch-sensitive surface 504, andevent dispatcher module 174 delivers the event information toapplication 136-1. A respective event recognizer 180 of application136-1 compares the event information to respective event definitions186, and determines whether a first contact at a first location on thetouch-sensitive surface corresponds to a predefined event or sub-event,such as selection of an object on a user interface. When a respectivepredefined event or sub-event is detected, event recognizer 180activates an event handler 190 associated with the detection of theevent or sub-event. Event handler 190 optionally utilizes or calls dataupdater 176 or object updater 177 to update the application internalstate 192. In some embodiments, event handler 190 accesses a respectiveGUI updater 178 to update what is displayed by the application.Similarly, it would be clear to a person having ordinary skill in theart how other processes can be implemented based on the componentsdepicted in FIGS. 1A-1B.

Receiving Information about Characteristics of Respective Vehicles

Users interact with electronic devices in many different manners,including using electronic devices to view and find geographic locationson a map. In some embodiments, a user can request directions from onegeographic location to another geographic location. In some embodiments,suggested directions between locations provided to the user in responseto the user's request can be customized based on the characteristics ofa user's vehicle. The embodiments described below provide ways forreceiving information about the characteristics of the user's vehicleand using the received information to provide customized routes.Receiving this information and customizing routes enhances the user'sinteractions with the electronic device and reduces the amount of timeneeded by a user to perform operations. Reducing operational timedecreases the power usage of the device and increases battery life forbattery-powered devices.

FIGS. 8A-8CC illustrate exemplary ways in which an electronic devicereceives information about characteristics of respective vehicles inaccordance with some embodiments of the disclosure. The embodiments inthese figures are used to illustrate the processes described below,including the processes described with reference to FIG. 9 . AlthoughFIGS. 8A-8CC illustrate various examples of ways an electronic device isable to perform the processes described below with respect to FIG. 9 ,it should be understood that these examples are not meant to belimiting, and the electronic device is able to perform one or moreprocesses described below with reference to FIG. 9 in ways not expresslydescribed with reference to FIGS. 8A-8CC.

FIG. 8A illustrates electronic device 500 displaying user interface 800(e.g., via a display device, via a display generation component, etc.).In some embodiments, user interface 800 is displayed via a displaygeneration component. In some embodiments, the display generationcomponent is a hardware component (e.g., including electricalcomponents) capable of receiving display data and displaying a userinterface. In some embodiments, examples of a display generationcomponent include a touch screen display (such as touch screen 504), amonitor, a television, a projector, an integrated, discrete, or externaldisplay device, or any other suitable display device that is incommunication with device 500.

In some embodiments, user interface 800 is a user interface of a mapapplication (e.g., an application in which a user is able to viewgeographic locations, search for locations, and/or request directionsfrom one location to another, similar to the map application describedabove with respect to FIG. 6A). In some embodiments, the map applicationis an application installed on device 500.

In some embodiments, user interface 800 includes a representation of amap including the current location of the electronic device. In FIG. 8A,user interface 800 does not include any suggested routes or drivingdirections and is optionally a default user interface of the mapapplication (e.g., in a browsing state) that includes location indicator804. In FIG. 8A, user interface 800 includes settings option 802 that isselectable to display a settings user interface. In some embodiments,user interface 800 includes location indicator 804 that represents thecurrent location of device 500 on the representation on the map. In someembodiments, device 500 displays user interface 806. In someembodiments, user interface 806 includes search field 808 for performinga search for a location or business. In some embodiments, user interface806 includes one or more shortcuts 810 that are selectable to search forand display the respective location associated with the respectiveshortcut. For example, the “Home” shortcut is selectable to display thelocation associated with “Home”, the “Work” shortcut is selectable todisplay the location associated with “Work”, and the “Gym” shortcut isselectable to display the location associated with “Gym”.

In FIG. 8A, device 500 determines that an application associated withvehicle 1 (e.g., Vehicle 1 app) is not currently installed on thedevice. In some embodiments, an application associated with Vehicle 1 isan application external to the map application (e.g., a third-partyapplication, an application provided by a manufacturer of Vehicle 1,etc.). In some embodiments, an application associated with Vehicle 1 isconfigured to receive and/or display information associated with Vehicle1. For example, the application is able to receive information from acomputer on Vehicle 1 or from a server (which in turns receiveinformation from a computer on Vehicle 1) about one or morecharacteristics of Vehicle 1. For example, the application is able toreceive the current fuel and/or charge level of the vehicle and/or isable to receive estimated driving range information (or determine theestimated driving range based on the current fuel and/or charge level)of the vehicle. In some embodiments, the application is able to receiveand/or maintain information about other characteristics of the vehicle,such as the make a model, the color, the vehicle dimensions, the climatecontrol status, the open or closed status of the doors, the current tirepressure, the airbag status, the emissions system status, etc. In someembodiments, the map application is able to receive information from theapplication associated with Vehicle 1. In some embodiments, the mapapplication receives information about Vehicle 1 for use in providingcustomized routes when traveling using Vehicle 1, similar to describedabove with respect to method 700. In some implementations, the mapapplication may receive information about Vehicle 1 from other sources.For example, a user can manually provide information to the mapapplication (e.g., manual entry from a user), the information can beembedded in a QR code (e.g., information about the vehicle itself, orinformation for how to communicate with a server or system to receiveinformation about the vehicle), an API call from the map application(e.g., by the map application, by device 500, etc.) to a computer system(e.g., a computer system associated with Vehicle 1), or other ways inwhich a user positively opts into sharing his or her vehicle informationwith the map application.

In FIG. 8A, because device 500 determines that no application associatedwith a particular vehicle is installed on the device, then userinterface 800 does not include an indication and/or button to link anapplication associated with a vehicle with the map application. In someimplementations, device 500 provides a way for the user to manuallyenter information to associate a vehicle with the map application. Insome implementations, device 500 provides a way for the user to specifyinformation about a vehicle, e.g., the vehicle manufacture, the vehicleVIN, or other identifying information, in order for the map applicationto communicate with a computer system (e.g., associated with thevehicle) in order to obtain vehicle data.

In FIG. 8B, the map application and/or device 500 has determined thatVehicle 1 App (e.g., an application associated with Vehicle 1) isinstalled on device 500. In some embodiments, in accordance with adetermination that the Vehicle 1 app is installed on device 500, userinterface 806 includes indication 812. In some embodiments, indication812 includes a description to connect the Vehicle 1 app with the mapapplication to get customized routes and/or charging suggestions.Additionally, or alternatively, user interface 806 includes anindication that a user can enter information about their specificvehicle in order to manually link the map application to the vehicle orto access a specific vehicle's computer system (e.g., through an API) tocomplete the linking process. In some embodiments, indication 812includes button 814 that is selectable to initiate the process to linkthe map application with the Vehicle 1 app. In the embodimentillustrated in FIG. 8B, Vehicle 1 is an electric vehicle. In someembodiments, indication 812 is displayed only if the map application isnot already linked with the Vehicle 1 app. In some embodiments,indication 812 is displayed only if the Vehicle 1 application is itselfconfigured to provide information about Vehicle 1 (e.g., the Vehicle 1app has been linked with Vehicle 1 and is able to receive and provideinformation about Vehicle 1). For example, if the Vehicle 1 app has beeninstalled on device 500 but has not been initiated or otherwise linkedto Vehicle 1 such that the Vehicle 1 app receives data about Vehicle 1,then indication 812 is optionally not displayed until such time that theVehicle 1 app is initiated and/or linked to Vehicle 1. In someembodiments, indication 812 is displayed even if the user has manuallyadded Vehicle 1 to the map application (optionally initiating a processto link the Vehicle 1 app with the map application will override orsupplement the information manually provided to the map application bythe user about Vehicle 1).

In some embodiments, indication 812 can be displayed in accordance witha determination that criteria other than that the Vehicle 1 app isinstalled are satisfied. For example, as described above, the mapapplication is able to receive information for a vehicle from one ormore external sources, such as an application that's installed on thesame device as the map application, from an external server, from acomputer system associated with a vehicle (e.g., a vehicle's on-boardcomputer system, such as the vehicle's ECU), etc. Thus, in someembodiments, device 500 can display indication 812 if device 500determines that any of these mechanisms for receiving information aboutthe user's vehicle are available. For example, if device 500 determinesthat device 500 is in communication with or able to communicate with theon-board computer system of a user's vehicle, then device 500 candisplay indication 812 to link the user's vehicle with the mapapplication. In such embodiments, in response to a user selection ofindication 812, device 500 can initiate the process to add the user'svehicle to the map application (optionally to pair device 500 with thevehicle's on-board computer system), as will be described in more detailbelow. In some embodiments, device 500 can display indication 812without requiring the satisfaction of the criteria described above. Insuch embodiments, in response to a user selection of indication 812, theuser can be presented with one or more options to link Vehicle 1 withthe map application (e.g., present the user with the option to providecommunication details to connect with a server associated with theuser's vehicle, present the user with the option to scan a QR code thatprovides communication details to connect with a server associated withthe user's vehicle, etc.). In some embodiments, the map application canaccess the information about the user's vehicle via an API call toanother application, to a server, to the vehicle's on-board computersystem, etc.

FIG. 8C illustrates an exemplary lock or wake screen user interface 816that includes notification 818. In some embodiments, notification 818 isdisplayed in accordance with a determination that the Vehicle 1 app isinstalled on device 500. In some embodiments, notification 818 includesa description to connect the Vehicle 1 app with the map application toget customized routes and/or charging suggestions. In some embodiments,selection of notification 818 initiates a process to link the mapapplication with the Vehicle 1 app (e.g., causes the map application tobe displayed, automatically navigated to a user interface for linkingthe Vehicle 1 app with the map application, such as the user interfaceshown in FIG. 8E). In some embodiments, notification 818 is displayedonly if the map application is not already linked with the Vehicle 1app.

In some embodiments, notification 818 is displayed on any user interfaceand is not limited to only a lock or wake screen user interface. Forexample, notification 818 can be displayed while device 500 isdisplaying a system user interface (e.g., the home screen userinterface, an application launching user interface, a settings userinterface) or a user interface of an application. In some embodiments,notification 818 can be displayed on a notification user interface(e.g., a user interface that includes one or more active notifications).In some embodiments, notification 818 is persistent and remainsdisplayed on the lock or wake screen user interface (optionally and onthe notification user interface) until a user manually dismissesnotification 818, until the user selects notification 818 and/or untilthe user links the Vehicle 1 app with the map application.

In FIG. 8D, a user input 803 d is received selecting button 814. In someembodiments, in response to user input 803 d, device 500 initiates aprocess to link Vehicle 1, (e.g., through the Vehicle 1 app) with themap application, as shown in FIG. 8E. In FIG. 8E, device 500 displaysuser interface 820. In some embodiments, user interface 820 is a userinterface for confirming linking of Vehicle 1 (e.g., through the Vehicle1 App) with the map application. In some embodiments, user interface 820includes an icon 822 that represents the Vehicle 1 app (e.g., the appicon). In some embodiments, user interface 820 includes description 824that explains that connecting Vehicle 1 (e.g., through the Vehicle 1App) with the map application allows the map application to receivecharacteristics of vehicle 1. In some embodiments, user interface 820includes button 826 and button 828. In some embodiments, button 826 isselectable to connect (e.g., add, link, register, etc.) Vehicle 1 withthe map application. In some embodiments, button 828 is selectable toterminate the process to link Vehicle 1 with the map application (e.g.,cancel the linking).

In FIG. 8E, a user input 803 e is received selecting button 826. In someembodiments, in response to receiving user input 803 e, device 500displays user interface 830. In some embodiments, user interface 830includes the vehicles that are associated with the Vehicle 1 App (e.g.,the application for which indication 812 was displayed). For example, aparticular vehicle application can be associated with multiple vehiclesand receive and provide information about multiple vehicles (e.g., ifthe vehicles are of the same make and model, if the vehicles are by thesame manufacturer, if the application is compatible with multiplevehicles, if the application is compatible with vehicles of differentmakes and/or models, etc.). In FIG. 8F, user interface 830 includeslisting 836-1 corresponding to Vehicle 1 and listing 836-2 correspondingto Vehicle 2. In such embodiments, the Vehicle 1 App is able to accessand provide information about Vehicle 1 and Vehicle 2 (e.g., Vehicle 1and Vehicle 2 are optionally the same make and/or model and/or bothVehicle 1 and Vehicle 2 are registered with the Vehicle 1 app). As shownin FIG. 8F, listing 836-1 includes icon 838-1 representing Vehicle 1 anddescription 840-1. In some embodiments, description 840-1 includes thename of the vehicle (or optionally the make and/or model of the vehicle)and the current charge status of Vehicle 1 (and optionally the currentestimated driving range). Similarly, listing 836-2 includes icon 838-2representing Vehicle 2 and description 840-2 that includes the name ofVehicle 2 and the current charge status of Vehicle 2 (and optionally thecurrent estimated driving range). The names of the vehicles and thecurrent charge statuses are optionally received from the Vehicle 1 app.In some embodiments, each listing includes an indication (e.g.,indication 842-1 and indication 842-2) indicating that the respectivevehicle will be added to the map application.

In FIG. 8F, user input 803 f is received on listing 836-2, thusde-selecting Vehicle 2 from being added to the map application, as shownin FIG. 8G. Thus, only Vehicle 1 will be added to the map application(e.g., the map application will only receive information about Vehicle 1and not Vehicle 2). In FIG. 8G, user input 803 g is received selectingaffordance 834 corresponding to a confirmation to add Vehicle 1. In someembodiments, in response to user input 803 g, Vehicle 1 is added to themap application and the Vehicle 1 app is linked with the mapapplication, as shown in FIG. 8H. In some embodiments, linking theVehicle 1 app allows the map application to receive information aboutVehicle 1 from a source external to the application. In someembodiments, the information is received from the Vehicle 1 app. In someembodiments, the information is received from a server external todevice 500 (e.g., linking the Vehicle 1 app with the map applicationprovided the map application with information and/or credentials tocommunicate with the external server).

It is understood that the above-described process of providing anindication and button to link the Vehicle 1 app with the map applicationcan be repeated for multiple applications that are associated with othervehicles. For example, in the embodiments described above, the Vehicle 1app is associated with Vehicle 1 and Vehicle 2. In addition to theVehicle 1 app, device 500 can have a Vehicle 3 app installed that isassociated with Vehicle 3. In such embodiments, an indication such asindication 812 can be displayed for linking the Vehicle 3 app with themap application (e.g., to add Vehicle 3 to the map application andenable the map application to receive information about Vehicle 3 fromthe Vehicle 3 app and/or an external source). In other embodiments,indication 812 is only displayed for one application associated with avehicle (e.g., only displayed once) and after performing theabove-described linking process, a user can manually initiate theprocess for other vehicle applications via a settings user interface ofthe map application (e.g., such as user interface 848 described below).

In FIG. 8H, user input 803 h is received selecting settings button 802.In some embodiments, in response to user input 803 h, device 500displays user interface 848 as shown in FIG. 8I. As shown in FIG. 8I,user interface 848 is a settings user interface for changing and/ormodifying one or more settings associated with the map application. Forexample, user interface 848 includes options 850, 852, 854, 856, 858,and 860 corresponding to different options and/or settings. In someembodiments, option 854 corresponds to the “My Vehicles” option and isselectable to display the vehicles that have been added to the mapapplication. In FIG. 8I, user input 803 i is received selecting option854. In response to user input 803 i, device 500 displays user interface862, as shown in FIG. 8J. User interface 862 corresponds to the “myvehicles” user interface, in which the vehicles that have beenregistered with, added to, and/or linked to the map application aredisplayed. As shown in FIG. 8J, user interface 862 includes listing 864corresponding to Vehicle 1 that was added according to the linkingprocess described above. In some embodiments, user interface 862includes listings of vehicles that were added to the map application viaa process other than the process to link the map application with anapplication associated with a vehicle.

In some embodiments, listing 864 includes an icon representing thevehicle, the name of the vehicle (e.g., user selected name, make, and/ormodel), and indication 866 that indicates the current charge leveland/or estimated driving range of the vehicle.

In FIG. 8J, user input 803 j is received selecting listing 864. In someembodiments, in response to user input 803 j, device 500 displays userinterface 868. User interface 868 corresponds to a settings userinterface for Vehicle 1. In FIG. 8K, user interface 868 includes icon870 and edit link 872. In some embodiments, icon 870 is a representationof Vehicle 1 and optionally has a visual characteristic based on avisual characteristic of Vehicle 1. For example, if Vehicle 1 is red,then the maps application is able to receive information indicating thatVehicle 1 is red from the external source (e.g., from the Vehicle 1app), and icon 870 includes a red car icon (e.g., without the userspecifying the color of the icon). In some embodiments, edit link 872 isselectable to view and/or change the color and/or pattern of Vehicle 1(e.g., away from the automatically populated color and/or pattern basedon the information received about Vehicle 1), as will be describedbelow.

In some embodiments, user interface 868 includes name field 874. In someembodiments, name field 874 is selectable to edit the name of Vehicle 1(e.g., cause display of a soft keyboard with which the user is able toedit and/or provide a desired name). In some embodiments, name field 874is pre-populated with a name provided by the Vehicle 1 app (e.g., themake and/or model of the car, a name selected by a user to the Vehicle 1app, etc.). In some embodiments, user interface 868 includes chargeroption 876-1 and charger option 876-2. Charger option 876-1 correspondsto the charging plug type of Vehicle 1 and is selectable to view and/oredit the charger types and/or available adapters, as will be describedin more detail below. In some embodiments, charger option 876-2corresponds to the charging network preference and/or compatibility withVehicle 1, and is selectable to view and/or edit the charging networksto charge Vehicle 1 with, as will be described in more detail below.

In some embodiments, user interface 868 includes app listing 878corresponding to the application that is associated with Vehicle 1(e.g., and linked with the map application). In some embodiments,selection of app listing 878 causes display of the applicationassociated with Vehicle 1. In some embodiments, user interface 868 doesnot include app listing 878 if Vehicle 1 was added via a process otherthan the app linking process described above (e.g., such as via manuallyadding the vehicle).

In some embodiments, user interface 868 includes manufacturerinformation 880-1 and model information 880-2 that includes informationabout the make and model of Vehicle 1, respectively. In someembodiments, the make and/or model information of Vehicle 1 is receivedfrom the Vehicle 1 app and thus manufacturer information 880-1 and modelinformation 880-2 is automatically populated upon linking the Vehicle 1app with the map application.

In FIG. 8L, a user input 803 l is received selecting edit link 872. Insome embodiments, in response to user input 803 l, device 500 displaysuser interface 882 for viewing and/or editing the visual characteristicsof Vehicle 1. In FIG. 8M, user interface 882 includes a plurality ofcolor options 886-1 to 886-18 that are selectable to set the color ofVehicle 1 (e.g., which is used as the color for icons that representVehicle 1, such as icon 884 and icon 870). In some embodiments, thecolor option that is selected in user interface 882 is initiallyautomatically populated based on color information received from theVehicle 1 app. For example, the Vehicle 1 app is able to provide the mapapplication with information about the visual characteristics of Vehicle1 and indicates to the map application that Vehicle 1 has a colorassociated with color option 886-16. Thus, color option 886-16 isautomatically selected. In some embodiments, a user is able to select adifferent color option from the list of color options and override thecolor option that is provided by the Vehicle 1 application. In someembodiments, the color options that are displayed in user interface 882are the only color options that are available for the specific make andmodel of the color (e.g., the map application receives all of theavailable color options from the Vehicle 1 app). In some embodiments,the color options that are displayed are generally available vehiclecolors and are not selected for display based on the available colorsfor the specific vehicle.

In FIG. 8N, returning to user interface 868, a user input 803 n isreceived selecting charger option 876-1. In some embodiments, inresponse to user input 803 n, device 500 displays user interface 888, asshown in FIG. 8O. In some embodiments, user interface 888 includeslisting 890 and adapter option 892. In some embodiments, listing 890indicates the default plug type of Vehicle 1. In some embodiments, thedefault plug type is the type of plug that is currently installed onVehicle 1. In some embodiments, the default plug type is automaticallyselected based on information received from the Vehicle 1 app. In someembodiments, listing 890 is selectable to change the installed plug type(e.g., if the user performed an after-market modification of the defaultplug type). In some embodiments, adapter option 892 is selectable to addone or more adapter plugs to the map application. An adapter plug isoptionally a mechanism/apparatus that converts the default plug type toone or more other plug types. For example, Plug Type 1 may be onlycompatible with charging stations that accept Plug Type 1, but would notbe compatible with charging stations that are only compatible with PlugType 2. Thus, a plug adapter can be used to convert Plug Type 1 to becompatible with Plug Type 2 (e.g., by changing the physicalcharacteristics of the plug, by changing the electrical characteristicsof a particular charging station to something that is compatible withVehicle 1, etc.).

In some embodiments, if the respective vehicle is not an electricvehicle, but rather, a vehicle of a different fuel type (e.g., gasolinevehicle, plug-in hybrid, E85 vehicle, etc.), then charger option 876-1optionally is not displayed on user interface 868 or user interface 888includes the default implement for use in refueling or recharging thevehicle, including an option for adding compatible adapters for therespective vehicle.

In FIG. 8O, user input 803 o is received selecting adapter option 892.In some embodiments, in response to user input 803 o, device 500displays user interface 894, as shown in FIG. 8P. User interface 894includes a list of adapters that are selectable to indicate to the mapapplication the adapters that the user has possession of. In someembodiments, the list of adapters includes only adapters that arecompatible with Vehicle 1 (e.g., only adapters that are compatible withthe vehicle (optionally not adapters that are not compatible with thevehicle), only adapters that are compatible with the vehicle's plug type(optionally not adapters that are not compatible with the vehicle's plugtype), etc.). In some embodiments, the list of adapters is received fromthe Vehicle 1 app. In some embodiments, the list of adapters includesall existing adapters for any plug type.

In FIG. 8P, a user input 803 p is received selecting adapter option896-2. In some embodiments, in response to user input 803 p, adapter 2is selected to be added as an available adapter for Vehicle 1, as shownin FIG. 8Q (e.g., represented by the check mark icon). In FIG. 8Q, auser input 803 q is received selecting adapter 896-3 corresponding toadapter 3. In some embodiments, in response to user input 803 q, adapter3 is also selected to be added as an available adapter for Vehicle 1, asshown in FIG. 8R.

In FIG. 8R, a user input 803 r is received selecting the “Done” option,thus completing the addition of Adapter 2 and Adapter 3, and dismissinguser interface 894, as shown in FIG. 8S. In FIG. 8S, user interface 888now includes adapter listing 898-1 and adapter listing 898-2corresponding to adapter 2 and adapter 3, respectively, that was added.In some embodiments, based on the plug type and the list of availableadapters, the map application is able to suggest charging stations thatare compatible with Vehicle 1 (e.g., compatible with Plug Type 1 and/orcan be made to be compatible with Plug Type 1 using Adapter 2 or Adapter3). In some embodiments, device 500 can provide a list of differentcompatible adapters for vehicles other than electric vehicles. Forexample, a respective hydrogen vehicle may be compatible with certainfuel pump types and may require certain adapters to refuel at particularhydrogen fuel stations.

In FIG. 8T, user input 803 t is received selecting charger option 876-2corresponding to charging networks. In some embodiments, in response touser input 803 t, device 500 displays user interface 899, as shown inFIG. 8U. In some embodiments, user interface 899 includes a list of oneor more charging networks that are in operation in the user's geography(e.g., in the country, in the state, in the municipality, in the region,etc.). In FIG. 8U, user interface 899 includes charging network 897-1,charging network 897-2, and charging network 897-3. As shown in FIG. 8U,charging network 897-3 is automatically initially populated, optionallybased on information received from the Vehicle 1 App. For example,Vehicle 1 may have a pre-existing relationship with charging network897-3 or may be compatible with charging network 897-3 (e.g., optionallyonly compatible with charging network 897-3). In some embodiments,charging network 897-3 may be the charging network recommended by themanufacturer of Vehicle 1. As shown in FIG. 8U, a user is able to selectany of the charging network listings to indicate to the map applicationthe charging network that the user would like to use to charge Vehicle1. In FIG. 8U, user input 803 u is received selecting charging network897-2. In response to selection of charging network 897-2, the mapapplication will suggest only charging stops for Vehicle 1 that arewithin charging network 897-2 (e.g., selection of a charging networkselects the respective charging network as the only compatible chargingnetwork). In some embodiments, in response to selection of chargingnetwork 897-2, the map application will suggest charging stops forVehicle 1 that are within both charging network 897-2 and chargingnetwork 897-3 (e.g., selection of a charging network toggles therespective charging network as a compatible charging network).

In some embodiments, if the respective vehicle is not an electricvehicle, but rather, a vehicle of a different fuel type (e.g., gasolinevehicle, plug-in hybrid, E85 vehicle, etc.), then charger option 876-2optionally is not displayed on user interface 868 or user interface 899includes options for networks of stations compatible with the respectivevehicle's fuel type (e.g., options corresponding to different gasstation brands, etc.). For example, for a gas vehicle, user interface899 can include options of different gas station brands that areselectable such that the map application will only suggest gas stationsof the selected gas station brands.

FIGS. 8V-8CC illustrate embodiments in which the map applicationdisplays information or suggestions based on the information receivedfrom the Vehicle 1 app (and/or defined in the vehicle settings userinterface, as previously described). It is understood that although theembodiments illustrated herein describe receive information from theVehicle 1 app, the information can be received from any source externalto the map application, such as a server external to device 500.

It is understood that although the description of the figures belowdescribe embodiments in which device 500 determines one or moresuggested routes and/or determines one or more suggested stops, thisdetermination can be performed by the navigation server or by acombination of device 500 and the navigation server, the results ofwhich are provided to device 500 for display in the user interface.

In FIG. 8V, device 500 displays user interface 800 while Vehicle 1 isselected. In FIG. 8V, user interface 800 is similar to user interface600 described in FIG. 6A and includes location indicator 883. In someembodiments, location indicator 883 has a visual characteristic based onthe visual characteristic of Vehicle 1. For example, in FIG. 8V,location indicator 883 has the same visual characteristic as the visualcharacteristic of icon 884 and color option 886-16 described above inFIG. 8M.

In FIG. 8V, a user input 803 v is received requesting directions fromthe current location to Destination 1. As described above with respectto method 700, in response to user input 803 v, device 500 displays oneor more suggested routes. In some embodiments, suggested route 887-1and/or suggested route 887-2 include one or more suggested stops torefuel and/or recharge Vehicle 1. As shown in FIG. 8W, the currentcharge level of Vehicle 1 is such that Vehicle 1 has a 20 mile range. Insome embodiments, the map application receives the current driving rangeinformation from the Vehicle 1 app (e.g., 20 mile range) and/or receivesthe current charge information from the Vehicle 1 app (e.g., 5% charge).Based on the received information, device 500 determines that a chargingstop is required and includes a charging stop on one or more of thesuggested routes. In some embodiments, the charging stop that isselected is within the charging network that was selected above in FIG.8U (e.g., that is optionally provided by the Vehicle 1 app) and that iscompatible with the plug type of Vehicle 1 (optionally with or withoutusing one of the available adapters). In some embodiments, the locationand existence of charging stops is received from the Vehicle 1 app orfrom a database other than the Vehicle 1 app. In some embodiments, ifthe user had selected a different set of adapters and/or had selected adifferent charging network, then the suggested routes and/or suggestedstops provided by device 500 can be different than those shown herein,based on whether particular charging stations are compatible withparticular adapters and/or based on whether a particular chargingstation is within the selected charging network. For example, in FIGS.6K-6L, the selected charging network is “Gigawatts” and thus thesuggested stop is within the “Gigawatts” charging network, whereas thesuggested stop of suggested route 887-1 is within the “Ionize” chargingnetwork (which is compatible with the adapters selected by the user inFIGS. 8P-8R).

Thus, as shown in FIG. 8W, the routes that are suggested to the user arebased on characteristics of Vehicle 1 that are received from the sourceexternal to the map application (e.g., the Vehicle 1 app or an externalserver).

FIG. 8W illustrates an embodiment similar to FIG. 6M in which a userinput 803 w is received requesting navigation using suggested route887-1. In some embodiments, in response to user input 803 w, device 500enters navigation mode and displays step-by-step and/or turn-by-turndirections to navigate along suggested route 887-1 to the destination.In some embodiments, while in navigation mode, device 500 displays arepresentation of the vehicle that is based on the characteristicsreceived from the external source. For example, in FIG. 8X, icon 873that represents the vehicle's current location can have the same coloras location indicator 883 and icon 884, which is based on the colorinformation received from the Vehicle 1 app. In some embodiments, icon873 does not have a color based on the color of the vehicle.

FIG. 8X illustrates an embodiment, similar to FIG. 6P, in which the userhas arrived at a suggested charging station. As shown in FIG. 8X, thesuggested charging station is within the charging network selected abovein FIG. 8U (e.g., the “Ionize” charging network). In FIG. 8X,instructions 877 indicate the adapter that is required to connectVehicle 1 with the charging station (e.g., “Adapter 2”). As describedabove, in some embodiments, device 500 only suggests the use of anadapter that the user and/or Vehicle 1 app has indicated is availablefor Vehicle 1.

FIG. 8Y illustrates an embodiment, similar to FIG. 6Q, in which device500 has determined that Vehicle 1 has begun charging. In someembodiments, device 500 receives information from Vehicle App 1 thatVehicle 1 has begun charging (e.g., receives charging and/or batterylevel information). In some embodiments, in accordance with adetermination that Vehicle 1 has begun charging, device 500 updatesinstructions 879 to display the amount of time remaining to charge tothe suggested level. In some embodiments, information 879 includes anindication of the current charge level.

FIG. 8Z illustrates an embodiment, similar to FIG. 6Q, in which Vehicle1 has been charged to 34%. In some embodiments, instructions 879 isupdated to reflect the updated charge status. For example, in FIG. 8Z,instructions 879 reads “8 minutes remaining”, which is based on theestimated time remaining to charge to 53% that is based on the chargingrate and/or based on the current charge level that is received from theVehicle 1 app.

FIG. 8AA illustrates an embodiment, similar to FIG. 6V, in which device500 is in navigation mode and device 500 determines, based on updatedcharge information, that a recharging stop is required to reach thedestination. In some embodiments, the map application receives, from theVehicle 1 app, updated charge information (e.g., 10% charge) and/orupdated driving range information (e.g., 20 miles, 40 miles, etc.) anddetermines that a recharging stop is required. In accordance with adetermination that a recharging stop is required, device 500 displays aproposed route that includes a suggested stop within the selectedcharging network (optionally that is compatible with the plug type ofVehicle 1).

It is understood that although the embodiments described above refer toan electric vehicle, this is merely exemplary and the above-describedfeatures are not limited to only electric vehicles. For example, theability to link the map application to an application associated with avehicle can be performed for a vehicle of any fuel type (e.g., gasolinevehicle, hybrid vehicle, plug-in hybrid, etc.), and the map applicationcan receive information about characteristics of vehicles of any fueltype. Similarly, the map application can determine (optionally thenavigation server can determine) suggested routes and/or suggested stopsbased on the type of fuel used by the selected vehicle (e.g., gasstations, electric vehicle charging stations, hydrogen refuelingstations, E85 stations, diesel stations, etc.).

FIGS. 8BB-8CC illustrate an embodiment in which the Vehicle 1 app isinstalled on device 500 but is not yet linked with the map application.In FIG. 8BB, user input 803 bb is received requesting directions fromthe current location to Destination 1 while the Vehicle 1 App isinstalled but not linked (e.g., Vehicle 1 is not selected and/or the mapapplication does not have access to information about the characteristicof Vehicle 1), similar to the embodiments described in FIGS. 6A-6B. Insome embodiments, in response to user input 803 bb, device 500 displayssuggested route 887-5 and suggested route 887-6. As shown in FIG. 8CC,suggested route 887-5 and suggested route 887-6 are selected and/ordetermined without regard to the characteristics of Vehicle 1. Thus, inFIG. 8CC, suggested route 887-5 is the fastest route from the device'scurrent location to Destination 1, without including any suggested stopsfor recharging and/or refueling, and suggested route 887-6 is analternative route to suggested route 887-5 that also does not includeany suggested stops for recharging and/or refueling. Thus, as shown,even though Vehicle 1 app is installed, because Vehicle 1 app is notlinked with the map application, the map application is not able toreceive information about the current characteristics of the Vehicle 1and does not provide suggested stops based on current characteristics ofVehicle 1 received from an external source. It is understood, however,that the map application is able to provide customized suggested stopsbased on other information that is not received from the Vehicle 1 appor an external source. For example, even if the Vehicle 1 app is notinstalled, a user is optionally able to manually add Vehicle 1 to themap application and provide license plate information and receivecustomized routes based on whether Vehicle 1 is or is not subject todriving restrictions, as described above with respect to FIGS. 6W-6FF.If, on the other hand, the Vehicle 1 app is linked to the mapapplication, the map application can optionally receive license plateinformation from the Vehicle 1 app and provide customized routes forVehicle 1 based on the received information.

FIG. 9 is a flow diagram illustrating a method 900 of receivinginformation about characteristics of respective vehicles in accordancewith some embodiments of the disclosure. The method 900 is optionallyperformed at an electronic device such as device 100, device 300, anddevice 500 as described above with reference to FIGS. 1A-1B, 2-3, 4A-4Band 5A-5H. Some operations in method 900 are, optionally combined and/orthe order of some operations is, optionally, changed.

As described below, the method 900 provides ways to receive informationabout characteristics of respective vehicles. The method reduces thecognitive burden on a user when interacting with a user interface of thedevice of the disclosure, thereby creating a more efficienthuman-machine interface. For battery-operated electronic devices,increasing the efficiency of the user's interaction with the userinterface conserves power and increases the time between batterycharges.

In some embodiments, an electronic device 500 in communication with adisplay generation component (e.g., a mobile device (e.g., a tablet, asmartphone, a media player, or a wearable device), or a computer,optionally in communication with one or more of a mouse (e.g.,external), trackpad (optionally integrated or external), touchpad(optionally integrated or external), remote control device (e.g.,external), another mobile device (e.g., separate from the electronicdevice), a handheld device (e.g., external), and/or a controller (e.g.,external), etc.) displays (902), via the display generation component, amap user interface of a map application, such as user interface 800 inFIG. 8A (e.g., a user interface that displays a representation of a mapof a given geographic location.

In some embodiments, the display generation component is a displayintegrated with the electronic device (optionally a touch screendisplay), external display such as a monitor, projector, television, ora hardware component (optionally integrated or external) for projectinga user interface or causing a user interface to be visible to one ormore users, etc.

In some embodiments, the user interface is a user interface of a mapapplication. In some embodiments, the map user interface is interactableby the user to view different geographic locations or change the zoomlevel of the map.

In some embodiments, the map user interface includes a representation ofa map (e.g., a representation of a geographic location) and respectiveinformation (904), such as suggested route 887-1 and suggested route887-2 in FIG. 8W (e.g., an icon that represents the electronic deviceand optionally indicates the determined current location of the device).In some embodiments, the respective information includes one or moreroutes for travelling from one location to another location. In someembodiments, the respective information is based on characteristics of avehicle (e.g., color, shape, size, model, mileage, fuel type, etc.). Insome embodiments, the respective information is based on the selectedmode of transportation.

In some embodiments, in accordance with a determination that receiving,by the map application, information corresponding to a characteristic ofa first vehicle (e.g., a current and/or real-time state orcharacteristic of the first vehicle) from a source external to the mapapplication is enabled (e.g., the map application has been configured toreceive information from an external source that affects the display ofthe directions and/or routes from the first location to the secondlocation), the respective information is first information, wherein thefirst information is based on the characteristic of the first vehiclereceived from the source external to the map application (906), such ascurrent driving range of Vehicle 1 in FIG. 8W (e.g., the one or moreproposed routes from the first location to the second location are basedon the received information).

In some embodiments, the external source is an application associatedwith the first vehicle, separate from the map application, that isinstalled on the electronic device. In some embodiments, the externalsource is a server (e.g., external to the electronic device) associatedwith the first vehicle, that provides information to the mapapplication. In some embodiments, the external source is anotherelectronic device (e.g., external to the electronic device but in wiredor wireless communication with the device). In some embodiments, thecurrent characteristic of the first vehicle includes fuel information(e.g., amount of gas available, amount of charge available), estimateddistance that can be traveled for the current fuel (or charge) level,the type of fuel the vehicle uses (or the type of charger required),and/or physical characteristics of the first vehicle such color, size,shape, etc.). In some embodiments, the information corresponding to thecharacteristic of the first vehicle is received from multiple sourcesthat are external to the map application (e.g., multiple applications,multiple servers, etc.). In some embodiments, the information isinformation other than the current location of the vehicle and/or one ormore geographic locations (e.g., landmarks, etc.). In some embodiments,the information includes the current location of the vehicle. In someembodiments, a particular source provides information of characteristicsof multiple vehicles (e.g., an application is associated with and isable to provide information about one or more vehicles). In someembodiments, the map application is configured to receive informationfrom multiple external sources. In some embodiments, each source isassociated with a different vehicle (e.g., a first applicationassociated with the first vehicle, a second application associated witha second vehicle, etc.).

In some embodiments, the proposed routes include a proposed stop torefuel and/or recharge. In some embodiments, the proposed routes includethe proposed stop because the current fuel level (or charge level)received from the external source does not allow the vehicle to reachthe destination without refueling (or recharging). In some embodiments,the proposed stop depends on the type of charging station or fuelstation needed to provide the vehicle with the charge or fuel required(e.g., a specific type of charging station, a specific type of gasstation that provides a specific type of fuel such as diesel or E85). Insome embodiments, the first information is a representation of the firstvehicle, such as an icon or model of the first vehicle that reflect thephysical characteristics (e.g., has color(s) and/or a shape that isrepresentative of the first vehicle). In some embodiments, the firstinformation is information other than location information (e.g.,current location of the vehicle, starting location for navigationdirections, destination location for navigation directions, landmarks,favorite locations, etc. In some embodiments, for each external sourcefor which the map application is receiving information from, the mapapplication is able to display information based on the characteristicfor the respective vehicle associated with the external source. Forexample, if the map application is configured to receive informationfrom a first application associated with a first vehicle, a secondapplication associated with a second vehicle, and a first serverassociated with a third vehicle, the map application is able to displayfirst information based on characteristics of the first vehicle receivedfrom the first application, second information based on characteristicsof the second vehicle received from the second application, and thirdinformation based on characteristics of the third vehicle received fromthe first server. In some embodiments, the first, second, and thirdinformation are displayed concurrently or are displayed individuallywhen the respective vehicles are selected in the map application.). Insome embodiments, the respective information includes an icon thatrepresents the user's vehicle (e.g., at a location on the representationof the map corresponding to the device's determined current location).In some embodiments, the icon has one or more visual characteristicsbased on the visual characteristics of the user's vehicle. In someembodiments, the icon is a cartoon or caricature of the user's vehicle.For example, the icon is a car having the same or similar color as thefirst vehicle and/or the same or similar shape as the first vehicle.

The above-described manner of displaying information based on receivedinformation on the characteristics of a particular vehicle (e.g., if themap application is enabled to receive information from a source externalto the map application) quickly and efficiently customizes informationfor a particular vehicle (e.g., by displaying information that is basedon the received current characteristics of the vehicle), whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., without requiring the userto separately determine whether the resulting information is appropriatefor the vehicle or perform additional inputs to manually edit proposedroutes to include required stops to refuel or recharge), whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiency while reducing errors in the usage of the device.

In some embodiments, the respective information and the firstinformation are of a respective type, such as the current driving rangein FIG. 8W (e.g., the respective type of information includes navigationdirections shown on the map, a representation of a vehicle on the map,etc.). In some embodiments, in accordance with a determination thatreceiving, by the map application, information corresponding to thecharacteristic of the first vehicle from the source external to the mapapplication is not enabled, the respective information is secondinformation of the respective type, wherein the second information isnot based on the characteristic of the first vehicle, such as suggestedroute 887-5 and suggested route 887-6 not being based on the drivingrange of any vehicle in FIG. 8CC (e.g., if the map application is notconfigured to receive information from the external source, then displayinformation that is not based on a characteristic of a particularvehicle. For example, the map application displays one or more genericproposed routes from the first location to the second location. In someembodiments, the generic proposed routes do not take into account fuelor charge levels of the first vehicle. In some embodiments, a genericicon or generic model of a vehicle is displayed (as opposed to an iconthat has visual characteristics based on the visual characteristics ofthe first vehicle). In some embodiments, the information displayed whenreceiving information by the map application is not enabled is the sametype of information displayed when receiving information by the mapapplication is enabled (e.g., the information is a route, but differentroutes, the information is an icon of a vehicle, but different icons,etc.).

The above-described manner of displaying information that is not basedon received information about a characteristic of a vehicle (e.g., ifthe map application is not enabled to receive information from a sourceexternal to the map application) quickly and efficiently provides eithergeneric map information or customized map information, which simplifiesthe interaction between the user and the electronic device and enhancesthe operability of the electronic device and makes the user-deviceinterface more efficient (e.g., by automatically providing customizinginformation if custom information is available, without requiring theuser to perform additional inputs to enable or disable custominformation), which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiency while reducing errors inthe usage of the device.

In some embodiments, the respective information is displayed in responseto a user input corresponding to a request to display directions from afirst location to a second location, such as user input 803 in FIG. 8V(e.g., a request to display one or more routes and/or directions from afirst geographic location to a second geographic location, and therespective information is one or more suggested routes for travellingfrom the first location to the second location).

For example, the user input requests driving directions from the firstlocation to the second location. In some embodiments, a user selects thefirst and/or second geographic location. In some embodiments, the firstor second geographic location is the determined current location of theelectronic device. In some embodiments, the map user interface displaysthe one or more determined routes from the first geographic location tothe second geographic location. In some embodiments, the one or moresuggested routes are displayed overlaid on the representation of themap.

The above-described manner of displaying customized routes based onreceived information on the characteristics of a particular vehiclequickly and efficiently customizes information for a particular vehicle(e.g., by displaying suggested routes that are based on thecharacteristics of the vehicle), which simplifies the interactionbetween the user and the electronic device and enhances the operabilityof the electronic device and makes the user-device interface moreefficient (e.g., by automatically using the information received fromthe external source, without requiring the user to separately determinewhether the resulting information is appropriate for the vehicle orperform additional inputs to manually edit proposed routes to includerequired stops to refuel or recharge), which additionally reduces powerusage and improves battery life of the electronic device by enabling theuser to use the electronic device more quickly and efficiency whilereducing errors in the usage of the device.

In some embodiments, the characteristic of the first vehicle includes acurrent estimated distance that the first vehicle is able to travel,such as the 20 mile range of Vehicle 1 in FIG. 8W (e.g., receiving, fromthe source external to the map application, the estimated driving rangeof the first vehicle). In some embodiments, the characteristic of thefirst vehicle includes the current charge level or the current fuellevel of the first vehicle. In some embodiments, respective informationis based on the estimated driving range of the first vehicle. Forexample, respective information includes one or more suggested routesand the one or more suggested routes optionally includes one or moresuggested stops to refuel or recharge the vehicle (e.g., if theestimated driving range is less than the travel distance of the one ormore suggested routes), as described above with respect to method 700.

The above-described manner of displaying information based on theestimated distance that the vehicle is able to travel quickly andefficiently displays customized travel information for a particularvehicle, which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient (e.g., withoutrequiring the user to separately determine whether the resultinginformation is appropriate for the vehicle), which additionally reducespower usage and improves battery life of the electronic device byenabling the user to use the electronic device more quickly andefficiency while reducing errors in the usage of the device.

In some embodiments, the characteristic of the first vehicle includes atype of charger compatible with the first vehicle, such as Adapter 2 inFIG. 8X (e.g., receiving, from the source external to the mapapplication, the type of chargers that can be used to charge the firstvehicle).

In some embodiments, different electric vehicle charging stations havedifferent plugs and/or are compatible with different types ofconnectors. In some embodiments, different electric vehicles havedifferent plugs and/or are compatible with different types ofconnectors. In some embodiments, adapters exist that allow electricvehicles to convert the plug installed on the electric vehicle to a plugtype that is compatible with respective charging stations. In someembodiments, the source external to the map application provides the mapapplication with information about what types of chargers are compatiblewith the first vehicle and optionally what adapters are compatible withthe first vehicle (e.g., to connect to the different types of chargers).In some embodiments, based on the information about what types ofchargers are compatible with the first vehicle, the map application isable to suggest charging stations that use the type of chargers that arecompatible with the first vehicle (e.g., via using an adapter or withoutrequiring an adapter). In some embodiments, the map application does notsuggest charging stations that do not use the type of chargers (e.g.,either with or without the use of an adapter) that are compatible withthe first vehicle.

The above-described manner of displaying information based on the typeof chargers that are compatible with a particular vehicle quickly andefficiently determines the charging stations that are compatible withthe first vehicle (e.g., by automatically determining whether thecharging stations uses charger types that are compatible with thevehicle), which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient (e.g., withoutrequiring the user to separately determine whether a suggested chargingstation is compatible with the user's vehicle), which additionallyreduces power usage and improves battery life of the electronic deviceby enabling the user to use the electronic device more quickly andefficiency while reducing errors in the usage of the device.

In some embodiments, the characteristic of the first vehicle includes avehicle type, such as the make and model of Vehicle 1 in FIG. 8N (e.g.,the source external to the map application provides information about amake, model, and/or color of the first vehicle). In some embodiments,the map application displays a representation of the first vehicle thatis based on the make, model, and/or color of the first vehicle. In someembodiments, the representation of the first vehicle is displayed on therepresentation of the map at the current determined location (e.g., viaone or more location sensors such as GPS) of the electronic device(e.g., traveling on a road, parked on a road, parked at a building,etc.). In some embodiments, the representation of the first vehicle isdisplayed at the current determined location of the first vehicle (e.g.,based on location information received from the source external to themap application). For example, an icon of the first vehicle is displayedin the map user interface that has a color similar to or the same as thecolor of the first vehicle. In some embodiments, the icon of the firstvehicle has a shape that is based on the make and model of the firstvehicle.

The above-described manner of receiving the type of vehicle for aparticular vehicle quickly and efficiently customizes information for aparticular vehicle (e.g., by displaying information that is based on thetype of vehicle that is selected), which simplifies the interactionbetween the user and the electronic device and enhances the operabilityof the electronic device and makes the user-device interface moreefficient, which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiency while reducing errors in the usage ofthe device.

In some embodiments, the characteristic of the first vehicle includes acurrent charge level of the first vehicle, such as the 15% and 34%charge levels in FIGS. 8Y and 8Z (e.g., receiving, from the sourceexternal to the map application, the current charge level or the currentfuel level of the first vehicle). In some embodiments, the respectiveinformation that is displayed includes the current charge level orcurrent fuel level based on the information received from the sourceexternal to the map application. In some embodiments, the respectiveinformation that is displayed includes one or more suggested routes andthe one or more suggested routes optionally includes one or moresuggested stops to refuel or recharge the vehicle that are selectedbased on the current charge level or current fuel level of the firstvehicle (e.g., if the current charge or fuel level will not allow thefirst vehicle to reach the destination without refueling or recharging),as described above with respect to method 700.

The above-described manner of displaying information based on thecurrent charge level of a particular vehicle quickly and efficientlycustomizes information for a particular vehicle (e.g., by displayingcustomized routes based on whether the current charge level is enough toreach the destination), which simplifies the interaction between theuser and the electronic device and enhances the operability of theelectronic device and makes the user-device interface more efficient(e.g., without requiring the user to separately determine whether thevehicle is able to reach the destination using the suggested route),which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiency while reducing errors in the usage of the device.

In some embodiments, the first information includes one or moresuggested routes to travel from the first location to the secondlocation using the first vehicle, such as suggested route 887-1 andsuggested route 887-2 in FIG. 8W (e.g., the respective information thatis displayed includes one or more suggested routes from the firstlocation to the second location). In some embodiments, the one or moresuggested routes are selected and/or determined based on the receivedinformation for the characteristic of the first vehicle. For example,the map application receives, from the external source, the estimateddriving range of the first vehicle and using the estimated driving rangeinformation, the map application may add one or more suggested stops torefuel or recharge the first vehicle. In some embodiments, the mapapplication may suggest different routes based on the estimated drivingrange of the first vehicle, such as a shorter route or a route that isconducive to higher efficiency (e.g., to save fuel or charge). In someembodiments, the map application may suggest different routes based onother characteristics of the first vehicle, such as the ability totraverse certain roads (e.g., if the vehicle is too tall, too tall, ortoo heavy, or any other driving restriction, such as those describedabove with respect to method 700).

The above-described manner of displaying suggested routes based onreceived information for a particular vehicle quickly and efficientlycustomizes information for a particular vehicle (e.g., by receivinginformation about a current state of a vehicle and using the receivedinformation to select suggested routes for the vehicle), whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., without requiring the userto separately determine whether the vehicle is able to travel along theroute without stopping to refuel or recharge and separately looking forappropriate refueling or recharging stations), which additionallyreduces power usage and improves battery life of the electronic deviceby enabling the user to use the electronic device more quickly andefficiency while reducing errors in the usage of the device.

In some embodiments, the characteristic of the first vehicle includes acurrent estimated distance that the first vehicle is able to travel, anda first suggested route of the one or more suggested routes includes asuggested stop to charge a battery of the first vehicle, such assuggested stop 885 in FIG. 8W (e.g., based on the received informationfor the estimated driving distance for the first vehicle for the firstvehicle's current fuel or charge level, a suggested route includes oneor more suggested stops (e.g., such as at a gas station or a chargingstation) to refuel or recharge the first vehicle).

In some embodiments, as described above with respect to method 700, astop to refuel or recharge the vehicle is suggested if the vehicle wouldnot reach the destination, would run out of fuel or charge beforereaching the destination, would reach the destination with less than athreshold amount of fuel or charge (e.g., less than 5%, 10%, 15%, 20%,25%, 30%, etc. amount of fuel or charge), and/or with less than athreshold amount of estimated driving range remaining (e.g., 5 miles, 10miles, 15 miles, 30 miles, 50 miles, etc. of remaining driving range).

The above-described manner of suggesting stops to recharge the vehiclebased on received information of the current estimated distance that thevehicle is able to travel quickly and efficiently suggests requiredstops to recharge the vehicle (e.g., by automatically determining that arecharging stop is required, finding an appropriate recharging station,and adding the recharging stop to the suggested routes), whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., without requiring the userto separately determine whether the vehicle is able to travel along theroute without stopping to refuel or recharge and separately looking forappropriate refueling or recharging stations), which additionallyreduces power usage and improves battery life of the electronic deviceby enabling the user to use the electronic device more quickly andefficiency while reducing errors in the usage of the device.

In some embodiments, in accordance with a determination that anapplication associated with the first vehicle, different from the mapapplication, is installed on the electronic device, the electronicdevice displays, in the map user interface, an affordance correspondingto the application associated with the first vehicle, such as button 814in FIG. 8D (e.g., before the first vehicle has been added to the mapapplication, determining that an application associated with the firstvehicle is installed on the device).

In some embodiments, the application associated with the first vehicleis a third-party application (e.g., such as from the vehicle'smanufacturer). In some embodiments, the application associated with thefirst vehicle is able to access and display information about the firstvehicle. For example, the application associated with the first vehiclehas access to the first vehicle's fuel or charge level, the firstvehicle's mileage, the first vehicle's driving efficiency, the firstvehicle's driving history, the first vehicle's tire pressure status, thefirst vehicle's estimated driving range, and/or any other vehicle statusinformation. In some embodiments, if the first vehicle is not yet addedto the map application (e.g., such as described above with respect tomethod 700) and/or if the application associated with the first vehicleis not yet linked with the map application, then the map user interfaceincludes a selectable option to link the application associated with thefirst vehicle with the map application. In some embodiments, if anapplication associated with the first vehicle is not installed on theelectronic device, then do not display an affordance to link the mapapplication with the application associated with the first vehicle.

In some embodiments, the electronic device receives, via one or moreinput devices, a user input selecting the affordance, such as in FIG.8D. In some embodiments, in response to receiving the user inputselecting the affordance, the electronic device initiates a process toenable the map application to receive information corresponding to thecharacteristic of the first vehicle from the application associated withthe first vehicle, such as in FIGS. 8E-8G (e.g., initiate a process tolink the map application with the application associated with the firstvehicle).

In some embodiments, linking the application associated with the firstvehicle with the map application enables information that is accessiblefrom the application associated with the first vehicle to be accessibleby and/or from the map application. In some embodiments, the mapapplication receives and/or accesses the information available to theapplication with the first vehicle to customize the informationdisplayed in the map user interface based on the received information.In some embodiments, the information is received from the applicationassociated with the first vehicle. In some embodiments, the informationis received from a server external to the electronic device (e.g., usinginformation received from the first application that enables the mapapplication to communicate with the server).

The above-described manner of displaying an affordance to link the mapsapplication with an application associated with a particular vehicle(e.g., if the application is determined to be installed on theelectronic device) quickly and efficiently provides the user with amethod for linking the map application with the application associatedwith the vehicle (e.g., by automatically determining that theapplication is installed and providing a selectable option to link themaps application with the application for the vehicle), which simplifiesthe interaction between the user and the electronic device and enhancesthe operability of the electronic device and makes the user-deviceinterface more efficient (e.g., without requiring the user to determinewhether information is accessible for the user's vehicle and thenperform additional inputs to enable the maps application to receiveinformation about the user's vehicle), which additionally reduces powerusage and improves battery life of the electronic device by enabling theuser to use the electronic device more quickly and efficiency whilereducing errors in the usage of the device.

In some embodiments, while displaying the respective information, theelectronic device receives, from the source external to the mapapplication, updated information about the characteristic of the firstvehicle, such as the updated charge information in FIG. 8AA (e.g.,information about the characteristic of the first vehicle iscontinuously or periodically updated). In some embodiments, the mapapplication periodically polls the source of the information for updatedinformation. In some embodiments, the source pushes updates to the mapapplication in response to determining that there is an update to thecharacteristic.

In some embodiments, in response to receiving the updated informationabout the characteristic of the first vehicle, the electronic deviceupdates the respective information based on the updated informationabout the characteristic of the first vehicle, such as the new suggestedroute 887-4 with a suggested stop in FIG. 8AA (e.g., based on thereceived updated information, update the displayed information using thereceived updated information). For example, while displaying one or moresuggested routes, if the map application receives updated informationabout the current driving range of the first vehicle, the mapapplication changes the suggested routes to take into account anychanges in the driving range (e.g., if the driving range decreases, asuggested stop may be added to the suggested routes). In someembodiments, if the updated information does not affect the displayedinformation (e.g., does not affect the suggested route, or is notrelevant to the suggested route), then the device does not update therespective information based on the updated information.

The above-described manner of displaying updated information about aparticular vehicle (e.g., while already displaying customizedinformation for the vehicle) quickly and efficiently provides up-to-dateinformation, which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient (e.g., withoutrequiring the user to perform additional inputs to refresh theinformation displayed to the user based on updated information), whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiency while reducing errors in the usage of the device.

In some embodiments, the updated information about the characteristic ofthe first vehicle includes a current charge level of the first vehicleand the updated information about the characteristic of the firstvehicle is received while the first vehicle is being charged, such asthe 15% and 34% charge level in FIGS. 8Y-8Z (e.g., the respectiveinformation is the current charge level or current fuel level of thefirst vehicle and while the first vehicle is being refueled orrecharged, the map application is able to receive the updated fuel orcharge levels and display the updated fuel or charge levels (and/orupdate estimated fuel or charge levels that are associated with certainsteps of a route, and/or determine the estimated time for refueling orrecharging the vehicle, and/or update the expected time of arrival atthe destination based on the fueling or charging rate)).

The above-described manner of displaying updated charge information asthe vehicle is charging quickly and efficiently provides up-to-datecharging information, which simplifies the interaction between the userand the electronic device and enhances the operability of the electronicdevice and makes the user-device interface more efficient (e.g., withoutrequiring the user to perform additional inputs to refresh the chargeinformation), which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiency while reducing errors inthe usage of the device.

In some embodiments, updating the respective information based on theupdated information about the characteristic of the first vehicle isperformed while providing navigation directions for the first vehicle,and includes updating the navigation directions based on the updatedinformation about the characteristic of the first vehicle, such as thenew proposed route with a new charging stop in FIG. 8AA. (e.g., whilenavigating along a suggested route such that step-by-step navigationdirections are displayed, updating or modifying the navigationdirections based on the updated information). For example, in accordancewith a determination that the driving range of the first vehicle is nolonger enough to reach the destination (e.g., based on updated drivingrange information received from the source), one or more stops may beadded to the navigation directions for the vehicle to recharge orrefuel.

The above-described manner of receiving updated information as thevehicle is navigating along a route quickly and efficiently monitors thestate of the vehicle to determine whether the route should be updated(e.g., by automatically receiving updated information and modifying thenavigation directions if the updated information suggests that thedirections should be modified), which simplifies the interaction betweenthe user and the electronic device and enhances the operability of theelectronic device and makes the user-device interface more efficient(e.g., without requiring the user to separately determine whether thenavigation directions provided to the user need to be modified andperforming additional inputs to manually modify the route or trigger arefresh of the suggested directions), which additionally reduces powerusage and improves battery life of the electronic device by enabling theuser to use the electronic device more quickly and efficiency whilereducing errors in the usage of the device.

In some embodiments, updating the navigation directions based on theupdated information about the characteristic of the first vehicleincludes adding a suggested stop to the navigation directions, such asin FIG. 8AA (e.g., adding one or more suggested stops at a gas stationor charging station if, based on the updated information, the devicedetermines that the first vehicle will not reach the destination withoutrefueling or recharging (or optionally will reach the destination withless than a threshold amount of fuel or charge (e.g., 5%, 10%, 15%, 20%,25%, 30%, etc. amount of fuel or charge) or less than a threshold amountof remaining driving range (e.g., 5 miles, 10 miles, 15 miles, 30 miles,50 miles, etc. of remaining driving range)).

The above-described manner of adding a suggested top based on updatedinformation for a particular vehicle (e.g., if the updated informationsuggests that a refueling or recharging stop is required to reach thedesired destination) quickly and efficiently monitors whether thevehicle will reach the destination (e.g., automatically receivingupdated information and determining whether the vehicle will still reachthe destination or whether a stop is required), which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient (e.g., without requiring the user to separately determinewhether a stop is required and performing additional inputs to find arefueling or recharging station and adding the stop to the navigationdirections), which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiency while reducing errors in the usage ofthe device.

It should be understood that the particular order in which theoperations in FIG. 9 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 700 and 1100) are also applicable in an analogous manner tomethod 900 described above with respect to FIG. 9 . For example, theoperation of the electronic device of receiving information aboutcharacteristics of respective vehicles described above with reference tomethod 900 optionally has one or more of the characteristics ofdisplaying customized navigation routes, anonymizing a vehicleidentifier, etc., described herein with reference to other methodsdescribed herein (e.g., methods 700 and 1100). For brevity, thesedetails are not repeated here.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., as described with respect to FIGS. 1A-1B, 3, 5A-5B) orapplication specific chips. Further, the operations described above withreference to FIG. 9 are, optionally, implemented by components depictedin FIGS. 1A-1B. For example, displaying operation 902 is, optionally,implemented by event sorter 170, event recognizer 180, and event handler190. Event monitor 171 in event sorter 170 detects a contact ontouch-sensitive surface 504, and event dispatcher module 174 deliversthe event information to application 136-1. A respective eventrecognizer 180 of application 136-1 compares the event information torespective event definitions 186, and determines whether a first contactat a first location on the touch-sensitive surface corresponds to apredefined event or sub-event, such as selection of an object on a userinterface. When a respective predefined event or sub-event is detected,event recognizer 180 activates an event handler 190 associated with thedetection of the event or sub-event. Event handler 190 optionallyutilizes or calls data updater 176 or object updater 177 to update theapplication internal state 192. In some embodiments, event handler 190accesses a respective GUI updater 178 to update what is displayed by theapplication. Similarly, it would be clear to a person having ordinaryskill in the art how other processes can be implemented based on thecomponents depicted in FIGS. 1A-1B.

Anonymizing Vehicle Identifiers

Users interact with electronic devices in many different manners,including using electronic devices to view directions from onegeographic location to another geographic location. In some embodiments,certain geographic locations implement driving restrictions in whichcertain cars may be prohibited from driving in a restricted region basedon one or more characteristics of the user's vehicle. For example, ageographic location may implement a driving restriction based on thevalues of a vehicle's license plate. In some embodiments, the electronicdevice provides an anonymized version of the vehicle's license plate toa navigation server to receive navigation routes that are customized forthe particular vehicle (e.g., that take into account the drivingrestriction). The embodiments described below provide ways foranonymizing the vehicle's license plate and transmitting the anonymizedlicense plate to the navigation server to preserve the user's privacy.Anonymizing the user's license plates ensures that the user's personalinformation is protected, enhances the user's interactions with theelectronic device, and reduces the amount of time needed by a user toperform operations. Reducing operational time decreases the power usageof the device and increases battery life for battery-powered devices.

FIGS. 10A-10P illustrate exemplary ways in which a vehicle identifier isanonymized in accordance with some embodiments of the disclosure. Theembodiments in these figures are used to illustrate the processesdescribed below, including the processes described with reference toFIG. 11 . Although FIGS. 10A-10P illustrate various examples of ways anelectronic device is able to perform the processes described below withreference to FIG. 11 , it should be understood that these examples arenot meant to be limiting, and the electronic device is able to performone or more processes described below with reference to FIG. 11 in waysnot expressly described with reference to FIGS. 10A-10P.

FIG. 10A illustrates electronic device 500 displaying user interface1000 (e.g., via a display device, via a display generation component,etc.). In some embodiments, user interface 1000 is displayed via adisplay generation component. In some embodiments, the displaygeneration component is a hardware component (e.g., including electricalcomponents) capable of receiving display data and displaying a userinterface. In some embodiments, examples of a display generationcomponent include a touch screen display (such as touch screen 504), amonitor, a television, a projector, an integrated, discrete, or externaldisplay device, or any other suitable display device that is incommunication with device 500.

In some embodiments, user interface 1000 is a user interface of a mapapplication (e.g., similar to user interface 800 described above withrespect to FIG. 8A). In some embodiments, the map application is anapplication installed on device 500.

In some embodiments, user interface 1000 includes a representation of amap including the current location of the electronic device. In FIG.10A, user interface 1000 does not include any suggested routes ordriving directions and is optionally a default user interface of the mapapplication (e.g., in a browsing state) that includes location indicator1002 that represents the current location of device 500 on therepresentation on the map. In FIG. 10A, device 500 also displays userinterface 1004. In some embodiments, user interface 1004 includes searchfield 1006 for performing a search for a location or business. In someembodiments, user interface 1004 includes one or more shortcuts 1050that are selectable to search for and display the respective locationassociated with the respective shortcut. For example, the one or moreshortcuts 1050 can include a “Home” shortcut that is optionallyselectable to display the location associated with “Home”, a “Work”shortcut that is optionally selectable to display the locationassociated with “Work”, and a “Gym” shortcut that is optionallyselectable to display the location associated with “Gym”.

In some embodiments, a driving restriction corresponds to a restrictionthat defines that a certain set of vehicles may travel withoutrestriction and a second set of vehicles are restricted from travel. Insome embodiments, other restrictions are possible (e.g., a first set ofvehicles must follow a certain set of rules or regulations while asecond set follows a different set of rules or regulations, or allvehicles with a certain characteristic(s) are restricted from travel,etc.). For example, if a particular region or set of roads arecontrolled by a driving restriction, certain vehicles with certaincharacteristics defined by the restriction may be restricted fromtraveling within the region (or on the roads), while other vehicleswithout those certain characteristics may not be restricted fromtraveling within the region (or on the roads). For example, arestriction can exist in which odd numbered license plates (e.g.,vehicles with license plates that end in an odd number) are prohibitedfrom driving in a particular location during particular times and dateswhile even numbered license plates (e.g., vehicles with license platesthat end in an even number) are not prohibited from driving at any time(or are prohibited from driving in the particular location during othertimes). In some embodiments, other vehicle identifiers are possible,such as the vehicle identification number (VIN). Another example of adriving restriction can be that vehicles over a particular gross weightare prohibited from driving on a particular highway during businesshours, while vehicles under the gross weight threshold are notprohibited from driving on the highway.

As used herein, a restricted region is a geographic area in which arespective driving restriction applies. For example, if a drivingrestriction indicates that odd numbered license plates are prohibitedfrom driving in a particular geographic area, but even numbered licenseplates are not prohibited from driving in the particular geographicarea, then that entire geographic area in which the restriction appliesis optionally referred to as a restricted region.

As shown in FIG. 10A, user interface 1004 includes indication 1008(e.g., sharing similar features as indication 812 described above withrespect to FIG. 8B). In some embodiments, indication 1008 includes adescription to add license plate information to the map application. Insome embodiments, indication 1008 includes button 1010 that isselectable to initiate the process to add license plate information tothe map application.

In some embodiments, indication 1008 is displayed in accordance with adetermination that device 500 is at or near a restricted region thatprohibits vehicle based on the license plate numbers of the vehicles(e.g., in the restricted region or within 10 miles, 30 miles, 50 miles,100 miles, etc. of a restricted region). In some embodiments, indication1008 is displayed if the map application does not yet have any licenseplate information. For example, after the user completes the process toadd a license plate to the map application (as will be described in moredetail below), indication 1008 is no longer shown in user interface1004. In some embodiments, indication 1008 is displayed even if the userhas previously added license plate information to the map application.

In some embodiments, a user is able to add license plate information tothe map application via a settings user interface for the mapapplication (e.g., without requiring indication 1008 be displayed inuser interface 1004). For example, a user is able to initiate theprocess to add a license plate by adding a vehicle to the mapapplication via a user interface for managing vehicles that have beenadded to the map application, similar to the user interface 862described above with respect to FIG. 8J. For example, user interface 862can include one or more options for adding vehicles, editing vehicles,and/or deleting vehicles from the map application. In such embodiments,a user is able to initiate a process to add a vehicle to the mapapplication and provide the license plate information for the addedvehicle (e.g., similar to the process for adding a license plate to themap application in response to selection of button 1010, describedbelow).

In some embodiments, providing the map application with license plateinformation allows the electronic device (e.g., device 500) to displayone or more suggested routes based on whether the user's vehicle isprohibited or not prohibited from traveling in the restricted region,similar to the process described above with respect to method 700. Insome embodiments, the suggested routes are determined by transmitting arequest for navigation routes to a navigation server (e.g., routingserver) and receiving, in return, one or more potential navigationroutes. In some embodiments, the navigation server is able to receiveanonymized license plate information (or other anonymized vehicleidentifiers, such as an anonymized VIN number, an anonymized serialnumber, etc.) and provide navigation routes based on whether theprovided anonymized vehicle identifier falls within the restriction(e.g., the vehicle is prohibited from driving in the restricted region)or outside of the restriction (e.g., the vehicle is not prohibited fromdriving in the restricted region).

As will be described in more detail below, device 500 is able to protectthe user's privacy by modifying one or more values of the user's vehicleidentifier (e.g., license plate, VIN number, etc.), thus anonymizing thevehicle identifier, before transmitting an anonymized vehicle identifierto the navigation server. In some embodiments, the vehicle identifierinformation provided by the user (e.g., the un-anonymized license plate,the actual license plate number, etc.) is stored on device 500 and isnever transmitted away from device 500. In some embodiments, the vehicleidentifier information provided by the user is deleted from device 500after the anonymized vehicle identifier is generated (e.g., in responseto generating the anonymized license plate or in response totransmitting the anonymized licensed plate to the navigation server.)

In FIG. 10A, user input 1003 a is received selecting button 1010. Insome embodiments, in response to user input 1003, device 500 initiates aprocess to add license plate information to the map application, asshown in FIG. 10B. In FIG. 10B, device 500 displays user interface 1012.User interface 1012 is optionally a splash page or introduction page foradding license plate information to the map application. For example,user interface 1012 can include introduction 1014 that describes theprocess of providing license plate information to the map applicationand/or the benefits of providing license plate information to the mapapplication. In some embodiments, user interface 1012 includes button1016 that is selectable to continue the process to add license plateinformation to the map application. In some embodiments, user interface1012 includes button 1018 that is selectable to terminate the process toadd license plate information to the map application. As describedabove, after terminating the process to add license plate information tothe map application, a user is able to initiate the process via asettings user interface for the map application.

In FIG. 10B, user input 1003 b is received by a user selecting button1016. In some embodiments, in response to user input 1003 b, device 500continues the process to add license plate information to the mapapplication and displays user interface 1020 as shown in FIG. 10C. Insome embodiments, user interface 1020 includes one or more options forselecting the geographic region in which the vehicle is registered. Forexample, option 1022-1 corresponds to region 1, option 1022-2corresponds to region 2, option 1022-3 corresponds to region 3, etc. Insome embodiments, different geographic regions can have differentlicense plate patterns or license plate values and providing the mapapplication with the respective region in which the vehicle isregistered allows the map application to verify that a license plate isvalid (e.g., has the correct number of digits, has valid values forrespective digits, etc.).

In some embodiments, device 500 prioritizes or otherwise visuallyemphasizes one or more regions based on the current location of device500. For example, in FIG. 10C, device 500 determines, via one or morelocation determination processes (e.g., GPS data, cellular towertriangulation, etc.), that device 500 is located in region 1. Thus, inaccordance with a determination that device 500 is located in region 1,user interface 1020 displays option 1022-1 corresponding to region 1 ata location on user interface 1020 separate from the options for otherregions, as shown in FIG. 10C. Thus, device 500 is able to suggest aregion to the user by displaying region 1 as the first option visuallydistinguished from the other regions, thereby increasing the efficiencyof the device by emphasizing the more likely option to the user.

In FIG. 10C, a user input 1003 c is received by selecting option 1022-2corresponding to region 2. In some embodiments, in response to userinput 1003 c, device 500 displays user interface 1024. In someembodiments, user interface 1024 is a user interface for entering alicense plate number. For example, in FIG. 10D, user interface 1024includes entry 1026 for entering a license plate number and entry 1028for selecting the vehicle's fuel type. In FIG. 10D, because the userselected region 2, device 500 is able to automatically determine thatvehicles registered in region 2 have the same first character and thusdevice 500 automatically populates entry 1026 with the first character1030 (e.g., a “beta” character). In some embodiments, device 500 can setthe number of digits of a license plate or restrict the available valuesfor respective digits based on the license plate pattern for theselected region.

It is understood that although FIG. 10D illustrates user interface 1024including entry 1026 corresponding to the license plate number and entry1028 corresponding to the fuel type, more or fewer entries are possibleand both entries need not be displayed. For example, if a geographicregion considers a vehicle's license plate number, but does not considera vehicle's fuel type when making a driving restriction determination,then user interface 1024 can include only a single entry for entering alicense plate number without including an entry for providing a fueltype. Similarly, if a geographic region considers a vehicle's fuel typebut not the vehicle's license plate number, then user interface 1024 caninclude only a single entry for providing the fuel type withoutincluding an entry for providing a license plate number. Otherembodiments for other characteristics of a vehicle and/or vehicleidentifiers are possible. In some embodiments, any combination and anynumber of entries are possible.

FIG. 10E illustrates an alternative embodiment in which user input 1003e is received selecting option 1022-1 corresponding to region 1. In someembodiments, region 1 has a different license plate pattern than region2. For example, in response to user input 1003 e, device 500 displaysuser interface 1024 with entry 1026 automatically populated with firstcharacter 1032 (e.g., a “theta” character) that is different than firstcharacter 1030, as shown in FIG. 10F. Thus, in the embodiments shown inFIGS. 10C-10F, license plates in region 1 all have “theta” as the firstcharacter and license plates in region 2 all have “beta” as the firstcharacter. It is understood that device 500 is able to adapt to anylicense plate pattern for any geographic region and automaticallypopulate one or more characters if respective digits of a license plateare fixed for a respective region.

In some embodiments, based on the determination that device 500 islocated in region 1, device 500 automatically selects option 1022-1corresponding to region 1 as the region of registration for the vehiclebeing added. In such embodiments, device 500 does not display userinterface 1020 and, instead, proceeds to user interface 1024 as ifoption 1022-1 corresponding to region 1 were selected.

In FIG. 10F, a user input 1003 f is received by a user selecting entry1026. In some embodiments, in response to user input 1003 f, device 500displays virtual keyboard 1036 for entering characters into entry 1026,as shown in FIG. 10G. For example, in FIG. 10G, the user has providedcharacters 1034 (e.g., by selecting keys on virtual keyboard 1036)which, in combination with first character 1032, corresponds to thelicense plate for the user's vehicle that will be added to the mapsapplication.

In FIG. 10G, a user input 1003 g is received selecting entry 1028. Insome embodiments, in response to user input 1003 g, device 500 displaysuser interface 1038, as shown in FIG. 10H. As shown in FIG. 10H, userinterface 1038 includes one or more options corresponding to differentfuel types. For example, option 1040-1 corresponds to a gasoline fueltype and option 1040-3 corresponds to a hybrid fuel type. In someembodiments, the options are scrollable to change the option that iscurrently selected. Thus, a user is able to select the fuel type orpower type for the user's vehicle. As will be discussed in more detailbelow, in some embodiments, a vehicle's fuel type can determine whetherone or more sets of driving restriction rules apply to the vehicle. Forexample, a first set of rules may apply to cars with a gasoline fueltype while a different set of rules may apply to electric vehicles.

In FIG. 10H, after having selected option 1040-3 corresponding to ahybrid fuel type (e.g., and thus populating entry 1028 with hybridoption 1042), a user input 1003 h is received by a user selecting option1044 to complete the process for adding the license plate to the mapapplication. In some embodiments in response to user input 1003 h,device 500 displays user interface 1025, as shown in FIG. 10I. In someembodiments, user interface 1025 includes entry 1026 and entry 1028populated with the user-provided values to confirm the license plate andfuel type details. In FIG. 10I, user input 1003 i is receivedcorresponding to a confirmation of the license plate and fuel typedetails. In some embodiments, in response to user input 1003 i, device500 adds the respective vehicle with the respective license plate andfuel type to the map application, and, optionally, provides anotification indication (e.g., pop-up 1048), such as shown in FIG. 10J.In some embodiments, device 500 displays user interface 1000corresponding to the map application. In some embodiments, pop-up 1048that indicates that the vehicle has been successfully added to the mapapplication. As shown in FIG. 10J, indication 1008 is no longer shown inuser interface 1000. In some embodiments, indication 1008 is only shownif the user has not previously added a license plate to the mapapplication. Although indication 1008 is no longer shown in userinterface 1000, a user is optionally able to initiate the process to adda license plate to the map application (e.g., add another license plate)via a settings user interface for the map application (e.g., similar touser interface 848 and/or 862 as described above with respect to FIGS.8I-8J). Although the above disclosure describes a process for providinglicense plate information to the map application (e.g., adding a licenseplate to the map application), it is understood that the same or asimilar process can be performed for adding other types of vehicleidentifiers and/or vehicle characteristics to the map application.

In FIG. 10K, a user input 1003 k is received requesting directions toDestination 1 (e.g., represented by icon 1058 in user interface 1000)while the currently active vehicle has a license plate of “θB32F92”. Asdiscussed above with respect to methods 700 and 900, a user is able toselect the currently selected vehicle from a list of vehicles. In someembodiments, characteristics of the currently selected vehicle is usedto determine one or more suggested navigation routes, as discussed abovewith respect to methods 700 and 900.

In some embodiments, in response to user input 1003 k corresponding to arequest for navigation routes (e.g., directions), device 500 determinesone or more suggested routes for the selected vehicle. In someembodiments, determining one or more suggested routes for the selectedvehicle includes transmitting a request for routes to a navigationserver or routing server. In some embodiments, the request for routescan include starting location and destination location information. Insome embodiments, the request for routes can include the license platenumber of the vehicle for which routes are requested.

As discussed above, in some embodiments, certain geographic regions canhave one or more driving restrictions. In some embodiments, the one ormore driving restrictions are based on one or more characteristics ofthe vehicle seeking to travel within the restricted region. The examplesdescribed herein illustrate a driving restriction that uses the valuesof a vehicle's license plate to define whether a vehicle is prohibitedor not prohibited from traveling within the restricted region during therestricted time period (although it is understood that other types ofdriving restrictions are possible). It is understood, however, thatalthough the example illustrated herein is based on the vehicle'slicense plate, a restriction can be based on any characteristic or anyidentifier of a vehicle and device 500 can determine one or more routesand/or perform the below-described anonymization process.

It may be desired, however, to avoid transmitting the user's vehicleidentifier information (e.g., a license plate number), away from device500 (e.g., to a navigation server). In some embodiments, avoidingtransmission of the user's vehicle identifier information advantageouslyprotects the user's privacy by not transmitting identifying informationoutside of device 500 and by not transmitting the user's driving historyor destination history outside of device 500. Thus, in some embodiments,device 500 anonymizes the user's vehicle identifier to generate ananonymized vehicle identifier that is transmitted to the navigationserver and safeguards the user's actual vehicle identifier informationwithin device 500.

FIG. 10L illustrate an exemplary method 1060 of anonymizing a licenseplate. At step 1064, an electronic device (e.g., device 500) receivesdriving restriction ruleset 1062 and determines, based on drivingrestriction ruleset 1062, the portions of the license plate that arerelevant to the respective driving restriction. In some embodiments,driving restriction ruleset 1062 is a simplified ruleset that has beengenerated from a full ruleset (e.g., as will be described in furtherdetail below with respect to FIGS. 10N-100 ). In some embodiments,driving restriction ruleset 1062 is a signed and encrypted package, aswill be described in further detail below with respect to FIGS. 10N-100. In some embodiments, a driving restriction ruleset 1062 includes oneor more rules that define which license plates are prohibited fromdriving in a restricted region and which license plates are notprohibited from driving in the restricted region. For example, a drivingrestriction ruleset can include a rule that indicates that odd licenseplates are prohibited from driving in the restricted region and evenlicense plates are not prohibited from driving in the restricted region.In some embodiments, step 1064 determines that a respective portion ofthe license plate is relevant to the respective driving restriction ifthe respective portion of the license plate can affect the determinationof whether the vehicle is prohibited or not prohibited from driving inthe restricted region. In some embodiments, step 1064 determines that arespective portion of the license plate is relevant to the respectivedriving restriction if a rule in the driving restriction ruleset 1062defines two different groups of values for the respective portion of thelicense plate (optionally without indicating whether the groups areprohibited or are not prohibited from driving in the restrictionregion). For example, if a respective rule indicates that odd licenseplates are prohibited while even license plates are not prohibited, thenat step 1064, the electronic device can determine that the last digit ofthe license plate is relevant (e.g., and optionally the other digits arenot relevant, if there are no other rules in driving restriction ruleset1062). In another example, if a respective rule asks whether the lastdigit of the license plate falls within a first set of values thatincludes only even values or a second set of values that includes onlyodd values, then at step 1064, the electronic device can determine thatthe last digit of the license plate is relevant (e.g., and optionallythe other digits are not relevant, if there are no other rules indriving restriction ruleset 1062).

In some embodiments, based on the determination from step 1064, method1060 processes the relevant portions of the license plate separatelyfrom the not relevant portions of the license plate. For example,relevant portions 1068 are processed at step 1072 and not relevantportions 1070 are processed at step 1074. At step 1072, the electronicdevice determines the set of valid values for the respective portion ofthe license plate that are within the same set as the user's actuallicense plate. For example, if a respective rule indicates that a firstset for the last digit of a license plate includes only even numbers anda second set includes only odd numbers, at step 1072, the device candetermine whether the last digit of the user's license plate is even orodd. If the last digit is even, then the device optionally determinesthat the last digit of the user's license plate is within the “even”group and that the set of values that includes the user's actual licenseplate consists of even values. On the other hand, if the last digit ofthe user's actual license plate is odd, then the device optionallydetermines that the last digit of the user's plate is within the “odd”group and that the set of valid values that includes the user's actuallicense plate consists of odd values.

Based on this determination, at step 1076, the device is able todetermine that, to maintain the same type of restriction, the deviceshould select a value from the respective set of values that includesthe value of the respective digit in the user's actual license plate.Thus, at step 1076, the electronic device selects a value from therespective set of values that includes the value of the respective digitin the user's actual license plate. For example, if the last digit ofthe user's actual license plate is odd, then the device optionallychooses an odd value for the last digit of the anonymized license plate.On the other hand, if the last digit of the user's actual license plateis an even number, then the device optionally chooses an even value forthe last digit of the anonymized license plate. In some embodiments, theselection is performed randomly (e.g., randomly selecting a value fromthe set of values). In some embodiments, the selected values aredifferent from the original value of the respective portion of theactual license plate. In some embodiments, the selected values are thesame as the original value of the respective portion of the actuallicense plate (e.g., if the set of values includes only one value—theactual value of the respective portion of the actual license plate). Insome embodiments, step 1076 is performed for each relevant portion ofthe license plate.

At step 1074, values for the not relevant portions 1070 of the licenseplate are selected. In some embodiments, because the rules indicate thatthe not relevant portions 1070 of the license plate are not divided intodifferent groups of values, the electronic device is able to selectamongst all valid values for the respective portion of the licenseplate. Thus, the device need not determine multiple different sets ofvalues to select amongst (e.g., as it does for relevant portions 1068,at step 1072). Therefore, the set of values to select from includes allvalid values for the respective portion of the license plate. In someembodiments, the electronic device need only select from the set ofvalid values, without regard to whether the values are within anyparticular set of values. Thus, at step 1074, the device optionallyrandomly selects amongst all possible valid values. In some embodiments,the selected values are different from the original value of therespective portion of the actual license plate. In some embodiments, theselected values are the same as the original value of the respectiveportion of the actual license plate. In some embodiments, step 1074 isperformed for each portion of the license plate that is not relevant tothe restriction.

At step 1078, after values for all portions of the license plate havebeen selected (e.g., via steps 1072 and 1076 or via step 1074), theelectronic device optionally generates the anonymized license plate bymerging the selected values into a single anonymized license plate. Insome embodiments, the anonymized license plate is transmitted to therouting or navigation server when a user requests navigation routes.

In some embodiments, method 1060 described above is performed inresponse to a request for navigation routes. For example, method 1060 isperformed every time the user requests routes and the anonymized licenseplate is discarded after completion of the request. In some embodiments,method 1060 is performed periodically (e.g., every day, every 30 days,every year, etc.). In some embodiments, method 1060 is performed everytime the electronic device receives a set of rules (e.g., from a rulesserver, from navigation server, etc.). In some embodiments, method 1060is performed every time the electronic device determines that the set ofrules has changed.

FIG. 10M illustrates an example method of generating an anonymizedlicense plate with an example driving restriction ruleset. In FIG. 10M,driving restriction ruleset 1062 includes a first rule that asks whetherthe last digit of the license plate is either a 3 or an 8, and a secondrule that asks whether the second digit of the license plate is a letterwithin the range of A-F or O-T. As shown in FIG. 10M, neither the firstrule nor the second rule defines whether the particular values indicatedresults in a driving prohibition or doesn't result in a drivingprohibition.

At step 1064, the electronic device determines from the first rule andthe second rule that the relevant portions 1068 of the license plateconsist of the second digit and the last digit. As shown, because thefirst rule asks whether the last digit is a 3 or 8, the electronicdevice is able to determine that the value of the last digit of thelicense plate is a factor in determining whether a vehicle is prohibitedor not prohibited from driving in a restricted region. Thus, theelectronic device optionally determines that the last digit is relevantto the driving restriction. Similarly, because the second rule askswhether the second digit is in the range of A-F or O-T, the electronicdevice is able to determine that the value of the second digit of thelicense plate is a factor in determining whether a vehicle is prohibitedor not prohibited from driving in a restricted region. Thus, theelectronic device optionally determines that the second digit isrelevant to the driving restriction. As shown in FIG. 10M, relevantportions 1068 includes the second digit of the license plate and thelast digit of the license plate.

Additionally, at step 1064, because driving restriction ruleset 1062does not include any more rules than the first rule or the second rule,the driving restriction ruleset 1062 does not care about the value ofthe first digit and the third through sixth digits of the license plate.Thus, the electronic device optionally determines that not relevantportions 1070 includes the first and third through sixth digits of thelicense plate.

At step 1072, the electronic device determines the set of values withinwhich to select values for the anonymized license plate. In theembodiment illustrated in FIG. 10M, because the second rule asks whetherthe second digit is within the range of A-F or O-T, the electronicdevice optionally determines that the values for the second digit areorganized into two sets: a first set that includes the values A-F andO-T (e.g., the set of values that fall “within” the second rule), and asecond set that includes the values G-M and U-Z (e.g., the set of valuesthat fall “outside” of the second rule). In the example illustrated inFIG. 10M, only letters are valid values for the second digit. Afterdetermining the sets of values for the second rule, the electronicdevice determines which of the sets of values is the set from which toselect values for the anonymized license plate. As described above, tomaintain the same restriction as the actual license plate, theelectronic device selects from the set of values that includes theactual value of the respective portion of the actual license plate.Thus, because the second digit of the actual license plate is a “B”, thevalue of the second digit of the actual license plate falls “within” thesecond rule. Thus, the electronic device determines that the set ofvalues to select from 1080 for the second digit is the set of valuesthat falls “within” the second rule (e.g., the set that includes thevalues A-F and O-T).

Similarly, because the first rule asks whether the last digit is a threeor an eight, the electronic device optionally determines that the valuesfor the last digit are organized into two sets: a first set thatincludes the values 3 and 8 (e.g., the set of values that fall “within”the first rule), and a second set that includes the values 0-2, 4-7, and9 (e.g., the set of values that fall “outside” of the first rule). Afterdetermining the sets of values for the first rule, the electronic devicedetermines which of the sets of values is the set from which to selectvalues for the anonymized license plate. As described above, to maintainthe same restriction as the actual license plate, the electronic deviceselects from the set of values that includes the actual value of therespective portion of the actual license plate. Thus, because the lastdigit of the actual license plate is a “2”, the value of the last digitof the actual license plate falls “outside” the first rule. Thus, theelectronic device determines that the set of values to select from 1080for the last digit is the set of values that falls “outside” of thefirst rule (e.g., the set that includes the values 0-2, 4-7, and 9).

At step 1076, after determining the set of values to select within, theelectronic device selects (optionally randomly) a value from within therespective sets. In FIG. 10M, with respect to the second digit, theelectronic device selects “Q” 1084-1 from the set of values thatincludes A-F and O-T. Thus, the selected value for the second digit istreated the same as the actual value of the second digit of the actuallicense plate and thus maintains the same restriction state as theactual license plate while simultaneously concealing the actual value ofthe second digit of the user's actual license plate. In FIG. 10M, withrespect to the last digit, the electronic device selects “6” 1084-2 fromthe set of values that includes 0-2, 4, 7, and 9. Thus, the selectedvalue for the last digit is treated the same as the actual value of thelast digit of the actual license plate and thus maintains the samerestriction state as the actual license plate while simultaneouslyconcealing the actual value of the last digit of the user's actuallicense plate.

At step 1074, the electronic device selects from within a set of allvalid values for the not relevant portions of the license plate. Forexample, the electronic device selects from within the set of all validvalues for the first digit, for the third digit, the fourth digit, thefifth digit, and the sixth digit of the license plate. In FIG. 10M, theelectronic device selects “0” for the first digit, “G” for the thirddigit, “6” for the fourth digit, and “Y” for the fifth digit. In someembodiments, the selection is a random selection amongst the validvalues. Thus, as shown in FIG. 10M, selecting a random value for arespective digit can result in selecting the same value (e.g., the firstdigit remained the same), or can result in selecting a letter when theoriginal value was a letter (e.g., the selected value for the thirddigit is “G” when the original value for the third digit is a “3”,assuming, for example, that both letters and numbers are valid valuesfor the third digit), or vice versa.

After performing step 1074 and/or step 1076 and selecting anonymizedvalues for all portions of a license plate (e.g., for all digits of alicense plate), at step 1078, the electronic device merges all of theanonymized values into a singular anonymized license plate. For example,the first digit of the anonymized license plate is “0” (e.g., selectedin step 1074), the second digit is “Q” (e.g., selected in step 1076),the third digit is “G” (e.g., selected in step 1074), the fourth digitis a “6” (e.g., selected in step 1074), the fifth digit is a “2” (e.g.,selected in step 1074), the sixth digit is a “Y” (e.g., selected in step1074), and the last digit is a “6” (e.g., selected in step 1076), thusresulting in a full anonymized license plate 1086 of “θQG62Y6”. Asshown, the anonymized license plate is able to protect the originalvalue of the user's license plate (“θB32F92”) while maintaining the samerestriction state as the original value of the user's license plate(e.g., will be treated the same by the navigation server as the user'sactual license plate). Thus, providing the anonymized license plate tothe navigation server when requesting navigation routes will result inthe same set of routes as if the electronic device provided the user'sactual license plate, while simultaneously maintaining the privacy ofthe user.

FIG. 10N illustrates an exemplary method 1090 of validating a drivingrestriction ruleset. In some embodiments, method 1090 is performed at aserver, such as a rules validation server. As will be described in moredetail below with respect to FIG. 10O, a rules validation server isoptionally a server that receives a set of rules, determines whether therules satisfy or violate certain criteria, and signs and/or encrypts therules if the rules are validated. In some embodiments, validating adriving restriction ruleset includes determining whether the drivingrestriction ruleset violates certain criteria (e.g., or whether adriving restriction ruleset satisfies certain criteria). In someembodiments, at step 1094, a rules validation server receives a fulldriving restriction ruleset 1092 and determines whether the rulesetviolates privacy criteria. In some embodiments, full driving restrictionruleset 1092 include one or more rules that define the set of vehiclesthat are prohibited from driving in the restricted region and the set ofvehicles that are not prohibited from driving in the restricted region.In some embodiments, the full driving restriction ruleset 1092 includesan indication of whether a respective set of values are prohibited fromdriving in the restricted region and whether a second respective set ofvalues are not prohibited from driving in the restricted region. In someembodiments, the full driving restriction ruleset 1092 optionallyincludes more information (e.g., more definitions, more rules, etc.)than the simplified driving restriction ruleset (e.g., such as drivingrestriction ruleset 1062 described above with respect to FIGS. 10L-10M).

In some embodiments, step 1094 includes step 1096 and step 1098. Forexample, determining whether full driving restriction ruleset 1092violates the privacy criteria includes determining the relevant portionsof the license plate implicated by the rules (step 1096) and determiningwhether there are more than a threshold number of relevant portions(step 1098). In some embodiments, at step 1096, the rules validationserver determines, from the full driving restriction ruleset 1092, theportions of the license plate that are relevant to the restrictedregion. In some embodiments, determining the relevant portions issimilar to the process described above with respect to step 1072, thedetails of which will not be repeated here for brevity. At step 1098,after determining the portions of the license plate that are relevant tothe restricted region, the validation server determines whether thereare more than a threshold number of portions that are relevant to therestricted region. If there are more than the threshold number ofportions, then the privacy criteria are optionally violated, and ifthere are less than the threshold number of portions, then the privacycriteria is optionally not violated. In some embodiments, the thresholdnumber of portions is a third of the digits of the license plate, halfof the digits, two thirds of the digits, three quarters of the digits,all of the digits, etc. For example, in the example illustrated in FIG.10M where the license plate has seven digits, if the validation serverdetermines that full driving restriction ruleset 1092 indicates that allseven digits of the license plate are relevant to the drivingrestriction, then the privacy criteria is optionally violated. In suchan example, if a driving restriction ruleset indicates that all digitsare relevant, then there exists a risk that the user's privacy will beviolated. For example, the anonymization process described above may notsufficiently anonymize the user's license plate to ensure that theuser's identity is not revealed and/or the user's privacy is notviolated. In some embodiments, if a driving restriction rulesetindicates that all digits are relevant, then it could indicate that thedriving restriction ruleset has been maliciously altered by aunvalidated entity. For example, the driving restriction ruleset may bedefective as a result of an error in transmission or the drivingrestriction ruleset may have been hacked in an effort to cause devicesto transmit user's full license plates to an unvalidated entity (e.g., amalicious entity). In such scenarios, it is desired to reject the fulldriving restriction ruleset and prevent electronic devices (e.g., suchas device 500) from transmitting license plates, anonymous or otherwise,outside of the electronic device.

In some embodiments, the validation server can perform privacyvalidation steps other than those illustrated in method 1090. Forexample, the validation server can determine whether the rules define aset of values for a respective portion of a license plate with less thana threshold number of valid values. For example, if a respective ruledefines a set of values to only include one value, then when performingthe anonymization process, an electronic device would be unable toproperly anonymize the user's license plate. For example, if a rulesetindicates that two thirds of the digits of a license plate are relevantand for each of those digits, every set of values only includes onevalue, then the anonymizing process described above would result in theexact same value for two thirds of the digits. Thus, the result would bean anonymized license plate that is still substantially the same as theoriginal license plate such that the user's privacy would be violated.Thus, in some embodiments, the rules validation server can determinethat the full driving restriction ruleset 1092 violates the privacycriteria.

Returning to step 1098, if the rules validation server determines thatthere are more than a threshold number of relevant portions (e.g., “Yes”branch), then the privacy criteria is violated, but if there are notmore than the threshold number of relevant portions (e.g., “No” branch),then the privacy criteria is not violated. In some embodiments, if theprivacy criteria is violated, then at step 1099, the rules validationserver rejects the full driving restriction ruleset 1092. In someembodiments, rejecting the full driving restriction ruleset 1092includes discarding the full driving restriction ruleset 1092, forgoinggenerating a simplified driving restriction ruleset from the fulldriving restriction ruleset 1092, and/or forgoing signing and/orencrypting the full or simplified driving restriction ruleset. In someembodiments, if a driving restriction ruleset is not validated (e.g., isrejected), then devices that depend on receiving a validated ruleset(e.g., such as the electronic devices described in FIGS. 10L-10M) arenot able to anonymize a user's license plate. In such embodiments, theelectronic device optionally forgoes anonymizing a user's license plateand forgoes providing customized navigation routes to the user. Forexample, the electronic device optionally only provides suggested routesthat are not customized (e.g., without regard to whether a drivingrestriction applies to the user's vehicle), such as described above withrespect to FIG. 6X.

At step 1907, if the privacy criteria is not violated, then the rulesvalidation server accepts the ruleset. In some embodiments, acceptingthe ruleset includes generating a simplified ruleset based on the fullruleset. In some embodiments, the simplified ruleset defines the sets ofvalues that are treated differently for the relevant portions of alicense plate, similar to driving restriction ruleset 1062 describedabove with respect to FIGS. 10L-10M. In some embodiments, afteraccepting the ruleset and/or generating the simplified ruleset, therules validation server signs the simplified ruleset at step 1095. Insome embodiments, signing the simplified ruleset includes encrypting thesimplified ruleset using a private key of the rules validation server.In some embodiments, when the encrypted simplified ruleset is receivedby an electronic device (e.g., such as device 500), the electronicdevice is able to decrypt the simplified ruleset using the public key ofthe rules validation server. In some embodiments, successfullydecrypting the simplified ruleset using he public key of the rulesvalidation server indicates that the rules are genuine and that theyhave been validated by the rules validation server (e.g., such that itis safe to use for anonymizing license plates to generate customizedroutes).

FIG. 10O illustrates an exemplary block diagram of ecosystem 1093,including the servers and/or devices and their interactions during theprocesses of validating rules, generating anonymous license plates, andproviding navigation routes. In some embodiments, ecosystem 1093includes rules server 1091, validation server 1087 (e.g., rulesvalidation server), navigation server 1083 (e.g., routing server) andclient electronic device 1081 (e.g., device 500). It is understood thatany of the servers illustrated herein can be combined into a singleserver.

In some embodiments, rules server 1091 is a rules repository server inwhich the full driving restriction ruleset 1089 is maintained and/orstored. In some embodiments, in response to a request for the fulldriving restriction ruleset 1089, rules server 1091 transmits the fulldriving restriction ruleset 1089 to validation server 1087. In someembodiments, validation server 1087 issues a request for the fulldriving restriction ruleset 1089 periodically (e.g., every day, every 15days, every 30 days, every 3 months, every 6 months, etc.). In someembodiments, rules server 1091 automatically pushes the full drivingrestriction ruleset 1089 to validation server 1087. In some embodiments,in response to receiving full driving restriction ruleset 1089,validation server 1087 validates full driving restriction ruleset 1089and generates a signed simplified ruleset 1085 (e.g., such as via method1090 described above with respect to FIG. 10N).

In some embodiments, the signed simplified ruleset 1085 is transmittedto navigation server 1083. In some embodiments, navigation server 1083stores and/or maintains the signed simplified ruleset 1085 and transmitsthe signed simplified ruleset 1085 (e.g., unmodified) to clientelectronic device 1081 (e.g., optionally in response to a request forthe signed simplified ruleset 1085 from client electronic device 1081).In some embodiments, client electronic device 1081 issues a request forsigned simplified ruleset 1085 periodically (e.g., every day, every 15days, every 30 days, every 3 months, every 6 months, etc.). In someembodiments, client electronic device 1081 issues a request for signedsimplified ruleset 1085 in response to a request, from a user, forsuggested navigation routes. In some embodiments, in response to arequest for suggested navigation routes, client electronic device 1081sends a request for navigation directions (e.g., navigation routes) tonavigation server 1083. In some embodiments, the request for navigationdirections sent to the navigation server 1083 includes the anonymizedlicense plate (e.g., that was generated via method 1060 described abovewith respect to FIGS. 10L-10M). In some embodiments, navigation server1083 generates one or more navigation routes using the received licenseplate (e.g., anonymized license plate). In some embodiments, navigationserver 1083 has access to the full driving restriction ruleset 1089(e.g., navigation server 1083 receives full driving restriction ruleset1089 from rules server 1091) and is able to determine whether thereceived license plate is prohibited or not prohibited from driving in arestriction region. In some embodiments, if the received license plateis prohibited from driving in the restricted region, navigation server1083 optionally only provides navigation routes that avoid therestricted region to client electronic device 1083. In some embodiments,navigation server 1083 provides both routes that avoid the restrictedregion and routes that do not avoid the restricted region (optionallywith an indication that the license plate provided to navigation server1083 is prohibited from traveling along the routes that do not avoid therestricted region. In some embodiments, navigation server 1083 takesinto account the time window for the restrictions in the drivingrestriction ruleset. For example, if respective driving restrictionsonly apply during business hours of business days (e.g., M-F from 8:00AM to 5:00 PM), then navigation server 1083 provides routes that avoidthe restricted region only if the request for routes is received withinbusiness hours (e.g., assuming the vehicle is prohibited). In someembodiments, the request for routes received from client electronicdevice 1083 indicates that time at which the vehicle is planning totravel and navigation server 1083 is able to determine whether theprovided license plate is restricted during the planned travel time andprovide the navigation routes accordingly.

FIG. 10P illustrates device 500 displaying one or more suggested routesthat were received from a navigation server (e.g., such as navigationserver 1083). As shown in FIG. 10P, the currently selected vehicle has alicense plate number of “θB32F92”, but has generated an anonymizedlicense plate number “θQG62Y6”, which was provided to the navigationserver to generate customized routes. As shown in FIG. 10P, device 500is displaying suggested routes 1071-1 and 1071-2. In some embodiments,suggested route 1071-1 is selected to avoid the driving restrictionbecause the navigation server has determined that the user's licenseplate is prohibited from driving in the restricted region. In someembodiments, suggested route 1071-2 is selected without regard to thedriving restriction. In some embodiments, device 500 receives suggestedroute 1071-2 from the navigation server as part of the original requestfor directions (e.g., which included the anonymized license plate) or aspart of a separate request for directions (e.g., which did not includeany license plate information, or which included a second anonymizedlicense plate that was selected to not be prohibited from driving in therestricted region). Thus, as shown in FIG. 10P, device 500 is able toanonymize the user's license plate, transmit the anonymized licenseplate to a navigation server, receive one or more navigation routes fromthe navigation server that avoid a restricted region (e.g., if the useris prohibited) and display the one or more navigation routes for theuser to view and select.

FIG. 11 is a flow diagram illustrating a method 1100 of anonymizing avehicle identifier in accordance with some embodiments of thedisclosure. The method 1100 is optionally performed at an electronicdevice such as device 100, device 300, and device 500 as described abovewith reference to FIGS. 1A-1B, 2-3, 4A-4B and 5A-5H. Some operations inmethod 1100 are, optionally combined and/or the order of some operationsis, optionally, changed.

As described below, the method 1100 provides ways to anonymize a vehicleidentifier. The method ensures that the user's personal information isprotected and reduces the cognitive burden on a user when interactingwith a user interface of the device of the disclosure, thereby creatinga more efficient human-machine interface. For battery-operatedelectronic devices, increasing the efficiency of the user's interactionwith the user interface conserves power and increases the time betweenbattery charges.

In some embodiments, an electronic device 500 with one or moreprocessors and memory (e.g., a mobile device (e.g., a tablet, asmartphone, a media player, or a wearable device), or a computer,optionally in communication with one or more of a mouse (e.g.,external), trackpad (optionally integrated or external), touchpad(optionally integrated or external), remote control device (e.g.,external), another mobile device (e.g., separate from the electronicdevice), a handheld device (e.g., external), and/or a controller (e.g.,external), etc.) receives (1102), via a communication device (e.g., acommunication subsystem, a wired or wireless communication subsystem,such as WiFi, ethernet, NFC, etc.), a set of rules associated with adriving restriction for a geographic area, such as driving restrictionruleset 1062 in FIG. 10L (e.g., receiving a set of rules that definewhich cars are prohibited from driving in a geographic area and/or whichcars are not prohibited from driving in a geographic area).

In some embodiments, the set of rules is received from an externalsource (e.g., a navigation server, a rules server, etc.). In someembodiments, the set of rules are a simplified set of rules thatindicate which digits of a license plate are relevant and define thesets of values for the relevant digits, optionally without definingwhether vehicles with the respective set of values are or are notprohibited from driving in the restricted area (e.g., without definingthe outcome or result of the sets of values). For example, thesimplified set of rules can indicate that the last digit is relevant tothe driving restriction (e.g., because the value of the last digitdetermines whether the car is prohibited or not prohibited) and thatcars with an even last digit are treated differently than those whoselast digits are an odd number. In some embodiments, the simplified rulesindicate that the cars with the last digit being even or odd areprohibited or not prohibited (e.g., the rules define the outcome orresult of the sets of values). In some embodiments, the simplified rulesmerely indicate that the even cars are in one group and the odd cars arein another group. Both embodiments are contemplated and can be processedby the method described herein. In some embodiments, the simplified setof rules can indicate that certain rules apply during certain timeperiods and don't apply during other time periods (e.g., the rules applyMonday through Friday during business hours, but not outside of thesetime periods). In some embodiments, multiple rules can exist and/or therules can be nested (e.g., the result of one rule can determine whetherto apply a second rule, etc.). In some embodiments, the simplified setof rules are simplified from a full set of rules. In some embodiments,the full set of rules are distilled by a server (e.g., navigationserver, rules server, etc.) into the simplified set of rules beforetransmitting the rules to the electronic device. In some embodiments,the rules are received in response to a request by the electronicdevice. In some embodiments, the rules are received when the userrequests navigation routes. In some embodiments, the rules areperiodically received from the server (e.g., every 30 minutes, everyhour, every 12 hours, every day, every week, every month, etc.).

In some embodiments, the electronic device determines (1104), such as atstep 1064 in FIG. 10L, using the set of rules, one or more firstportions of an identifier of a vehicle that are relevant to the drivingrestriction (1106), such as relevant portions 1068 in FIGS. 10L and 10M(e.g., determining the digits that are relevant to the drivingrestriction), wherein the identifier of the vehicle is stored on theelectronic device, and the one or more first portions of the identifierare populated with one or more first values (e.g., the vehicle's licenseplate information is stored on the electronic device).

In some embodiments, a relevant digit is one whose value can affect thedetermination of whether the respective vehicle is prohibited or notprohibited. In the example given above in which a vehicle is prohibitedif the last digit is even, but not prohibited if the last digit is odd,the device is able to determine from this rule that the last digit of alicense plate is relevant to the driving restriction because the valueof the last digit dictates whether the respective vehicle is prohibitedor not prohibited from driving in a restricted region. In someembodiments, multiple digits can be determined to be relevant. Forexample, if the set of rules includes a first rule that asks whether thelast digit is even or odd and a second rule that asks whether the firstdigit is between A-M or N-Z, then both the first and last digits of thelicense plate are relevant. In some embodiments, the vehicle's licenseplate information is provided by the user. In some embodiments, thevehicle's license plate information is automatically populated frominformation received from an external source, such as via the methoddescribed above with respect to method 900.

In some embodiments, the electronic device determines, using the set ofrules, one or more second portions of the identifier of the vehicle thatare not relevant to the driving restriction (1108), such as not relevantportions 1070 in FIGS. 10L and 10M (e.g., determining the digits thatare not relevant to the driving restriction). In some embodiments,digits that are not relevant to the driving restriction are those thatdo not affect the determination of whether the respective vehicle isprohibited or not prohibited. For example, if the only rule in the setof rules asks whether the last digit is even or odd, then all otherdigits in a vehicle's license plate are not relevant to the drivingrestriction. In another example, if the set of rules includes a firstrule that asks whether the last digit is even or odd and a second rulethat asks whether the first digit is between A-M or N-Z, then the digitsof the vehicle's license plate other than the first and last digit arenot relevant to the driving restriction.

In some embodiments, the electronic device generates (1110) ananonymized identifier corresponding to the identifier of the vehicle,such as anonymized license plate “θQG62Y6” in FIG. 10M (e.g., based onthe determination of the relevant digits and the digits that are notrelevant, generate a license plate for a vehicle that is a proxy for theactual license plate with respect to the driving restriction thatprotects the user's actual license plate number from being sent out fromthe device), wherein the anonymized identifier includes one or morethird portions corresponding to the one or more first portions, and oneor more fourth portions corresponding to the one or more second portions(e.g., the anonymized license plate has digits that correspond to thedetermined relevant portions of a license plate and digits thatcorrespond to the determined not relevant portions of the licenseplate).

In some embodiments, the anonymized identifier is generated every time auser requests navigation routes (and optionally is discarded after therequest is completed). In some embodiments, the anonymized identifier isgenerated every time the device receives a set of driving restrictionrules. In some embodiments, the anonymized identifier is generated everytime the device receives an updated set of driving restriction rules(e.g., in accordance with a determination that the set of drivingrestriction rules have changed).

In some embodiments, generating the anonymized identifier includesselecting, for the one or more third portions, values selected from afirst set of values that correspond to the one or more first valuesbased on the set of rules, wherein the first set of values is a subsetof a set of valid values for the one or more third portions (1112), suchas selecting “Q” from the set of values including A-F and O-T and “6”from the set of values including 0-2, 4-7, and 9 in step 1076 of FIG.10M (e.g., for the digits that have been determined to be relevant tothe driving restriction, selecting a value from the set of values thatare in the same group as the actual value of the respective licenseplate).

For example, if the rule asks whether the last digit is even or odd,then if the last digit of the user's actual license plate is odd, thenthe device selects an odd value as a proxy for the actual value for thelast digit of the user's license plate. In some embodiments, selecting avalue from the same group as the user's actual value allows the deviceto ensure that the anonymized license plate is still subject to the samerestrictions as the user's actual license plate. In some embodiments,the selected value is a different value than the actual value of therespective digit of the user's license plate. In some embodiments, theselected value is the same value as the actual value of the respectivedigit of the user's license plate.

In some embodiments, generating the anonymized identifier includesselecting, for the one or more fourth portions, random values from a setof valid values for the one or more fourth portions (1114), such asselecting the values “0” “G”, “6”, “2”, and “Y” from the set of allvalid values at step 1074 in FIG. 10M (e.g., for the digits that havebeen determined to not be relevant to the driving restriction, selectinga value from all valid license plate values (for the respectivedigits)).

In some embodiments, selecting the value includes randomly selecting avalue from all valid license plate values. In some embodiments, the setof valid values for the respective digits are received from an externalsource (e.g., a navigation server, a rules server, etc.). In someembodiments, the selected value is a different value than the actualvalue of the respective digit of the user's license plate. In someembodiments, the selected value is the same value as the actual value ofthe respective digit of the user's license plate. In some embodiments,after selecting the values for the one or more third portions and theone or more fourth portions, the anonymized license plate is generatedby combining the selected values into a single licensed plate. In someembodiments, the anonymized license plate has the same restricted stateas the original license plate. For example, if the original licenseplate would otherwise have been prohibited from driving in therestriction zone, then the anonymized license plate is also prohibitedfrom driving in the restriction zone (and vice versa). Thus, theanonymized license plate has the same restriction state as the actuallicense plate. In some embodiments, ensuring that the anonymized licenseplate has the same restriction state as the actual license plate ensuresthat the anonymized license plate is treated similarly as the actuallicense plate when requesting navigation routes from a navigationserver. For example, if the navigation server receives a license platewith the request for navigation routes and determines the availableroutes for the vehicle based on whether the license plate is prohibitedor not prohibited from the restricted region, providing the navigationserver with an anonymized license plate that is also prohibited fromdriving in the restricted region (e.g., if the actual license plate isprohibited from the restricted region) ensures that the navigationserver provides the same or similar navigation routes as if the devicehad provided the vehicle's actual license plate, without requiring thedevice to transmit the user's actual license plate away from the device.

In some embodiments, the electronic device transmits (1116), via thecommunication device, the anonymized identifier to a routing server forgenerating a driving route in the geographic area, wherein theidentifier of the vehicle is not transmitted to a destination externalto the electronic device, including the routing server, such as therequest for navigation directions 1077 in FIG. 10O (e.g., transmittingthe anonymized license plate to a routing server that determines, basedon the provided license plate, the routes that are available for therespective vehicle).

In some embodiments, the anonymized identifier is transmitted with arequest to provide routes from a first geographic location to a secondgeographic location. Thus, in some embodiments, after transmitting theanonymized identifier, the device receives, from the routing server, oneor more potential driving routes from the first geographic location tothe second geographic location. In some embodiments, requestingnavigation routes from the routing server includes transmitting theanonymized license plate, and origin and destination locationinformation. In some embodiments, in response to requesting thenavigation routes, the device receives, from the navigation server, oneor more navigation routes (optionally selected based on whether theanonymized license plate is prohibited or not prohibited from driving inthe restricted region). In some embodiments, the one or more potentialdriving routes can be selected by the routing server to avoid therespective driving restriction if the received identifier indicates thatthe user's vehicle is prohibited from driving in the restricted region.In some embodiments, the one or more driving routes received from therouting server can be displayed in a map user interface, similar todescribed above with respect to method 700. In some embodiments, therouting server only provides routes that are not prohibited by thedriving restriction. Thus, in some embodiments, the device performs theabove anonymizing method twice: once to generate routes for a restrictedvehicle (e.g., an anonymized identifier that falls within one group ofidentifiers that results in routes that avoid the restriction), and onceto generate routes for an unrestricted vehicle (e.g., an anonymizedidentifier that falls within the other group of identifiers that resultsin routes that ignore the restriction) to provide the user with theoption of avoiding the restriction or ignoring the restriction, asdescribed above with respect to method 700. In some embodiments, theanonymized identifier is generated every time the user requests routesthat are affected by a driving restriction. In some embodiments, theanonymized identifier is generated every time a new set of rules isreceived (e.g., the device optionally determines whether the new set ofrules is different than the previous set of rules and generates a newanonymized identifier accordingly). In some embodiments, the vehicle'soriginal license plate number is not transmitted away from theelectronic device as part of the process to determine navigation routes.In some embodiments, the vehicle's original license plate number isnever transmitted away from the electronic device as a part of any mapor navigation process.

The above-described manner of requesting routes from a routing serverfor a particular vehicle (e.g., by anonymizing the vehicle's licenseplate based on a set of driving restriction rules and transmitting theanonymized license plate to the routing server to generate potentialroutes) provides a quick and efficient way of obtaining applicabledriving routes without jeopardizing the privacy of the user of theelectronic device or vehicle, which simplifies the interaction betweenthe user and the electronic device and enhances the operability of theelectronic device and makes the user-device interface more efficient(e.g., by protecting the user's privacy by automatically anonymizing theuser's license plate, without requiring the user to manually anonymizethe vehicle's license plate before transmission to the routing server),which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiency while reducing errors in the usage of the device.

In some embodiments, the identifier of the vehicle is a license platenumber of the vehicle, such as license plate number “θB32F92”illustrated in FIG. 10L (e.g., the respective driving restriction isbased on the license plate number of the vehicle). For example, if adriving restriction ruleset indicates that if a vehicle's license platematches certain criteria, the vehicle is prohibited from driving in arestricted region and if the vehicle's license plate does not match thecriteria, the vehicle is not prohibited from driving in the restrictedregion. In some embodiments, the identifier can be other types ofidentifiers (e.g., unique or not unique). For example, if the respectivedriving restriction is based on a color of the vehicle, then theidentifier is the vehicle's color. In another example, if the respectivedriving restriction is based on the type of vehicle (e.g., sedan, SUV,truck, minivan, semi-trailer truck, etc.), then the identifier is thetype of vehicle. In some embodiments, the identifier includes a vehicleidentification number (VIN). In some embodiments, the identifierincludes the fuel or power type of the vehicle (e.g., gas vehicle,hybrid vehicle, plug-in hybrid vehicle, electric vehicle, etc.).

The above-described manner of requesting routes from a routing serverfor a particular vehicle (e.g., by anonymizing the vehicle's licenseplate based on a set of driving restriction rules and transmitting theanonymized license plate to the routing server to generate potentialroutes) provides a quick and efficient way of obtaining applicabledriving routes without jeopardizing the privacy of the user of theelectronic device or vehicle, which simplifies the interaction betweenthe user and the electronic device and enhances the operability of theelectronic device and makes the user-device interface more efficient(e.g., by protecting the user's privacy by automatically anonymizing theuser's license plate, without requiring the user to manually anonymizethe vehicle's license plate before transmission to the routing server),which additionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiency while reducing errors in the usage of the device.

In some embodiments, the electronic device determines that a respectiveportion of the one or more first portions cannot be changed, such as instep 1072 in FIG. 10L (e.g., determining that the driving restrictionrequires that a respective digit of the license plate not beanonymized). In some embodiments, a respective digit of the licenseplate cannot be anonymized if the determined set of valid values for therespective digit only includes one value (e.g., the value of therespective digit of the actual license plate). For example, if arespective digit (e.g., the first digit) of a license plate is anindicator of the region in which the vehicle is registered, then arespective rule that asks whether the vehicle is registered in aparticular region results in a determination that the first digit of thelicense plate cannot be anonymized (if, for example, the first digit ofthe actual license plate indicates that the vehicle is indeed registeredin the particular region).

In some embodiments, generating the anonymized identifier furtherincludes selecting, for a respective portion of the one or more thirdportions corresponding to the one or more first portions, a value of therespective portion of the one or more first portions, such as in step1076 in FIG. 10L (e.g., if the driving restriction requires that arespective digit of the license plate cannot be anonymized or masked,then the respective digit for the anonymized license plate has the samevalue as the original license plate).

For example, if a rule asks whether the first digit is an “A” or not an“A”, and the first digit of vehicle's original license plate is an “A”,then the set of valid values for the first digit only includes the value“A” and thus, the resulting anonymized license plate has “A” for itsfirst digit. Thus, in some embodiments, depending on the rules in thedriving restriction ruleset, one or more digits of the license plate canhave the same value as the original license plate. In some embodiments,the other digits of the license plate that do not result in a set ofvalid values of just one value are able to be anonymized as describedabove (e.g., which optionally results in an anonymized digit that aredifferent value than the original license plate).

The above-described manner of anonymizing the identifier of the vehicle(e.g., by selecting the same value as the original license plate if adriving restriction requires that a respective digit not be changed)provides a quick and efficient way of obtaining applicable drivingroutes without jeopardizing the privacy of the user of the electronicdevice or vehicle (e.g., by maintaining the same restriction state asthe original license plate, including maintaining the same value forrespective digits of the license plate if the driving restrictionrequires it), which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient (e.g., by protectingthe user's privacy by automatically anonymizing the user's licenseplate, without requiring the user to manually anonymize the vehicle'slicense plate before transmission to the routing server), whichadditionally reduces power usage and improves battery life of theelectronic device by enabling the user to use the electronic device morequickly and efficiency while reducing errors in the usage of the device.

In some embodiments, the set of rules includes a first rule that definesa first set of values for a first respective portion of the identifier(e.g., a first rule defines a first set of values for a respectiveportion of the identifier (e.g., a respective digit of a license plate)that have a first driving restriction result) and a second set ofvalues, different from the first set of values, for the first respectiveportion of the identifier, such as the first rule in driving restrictionruleset 1062 in FIG. 10M that defines a first set of values thatincludes “3” and “8” and a second set of values that includes 0-2, 4-7,and 9 (e.g., the first rule defines a second set of values for therespective portion of the identifier (e.g., the respective digit of alicense plate) that have a second driving restriction result, differentfrom the first driving restriction result).

In some embodiments, the first rule defines a first set of values thatare prohibited from driving. In some embodiments, the set of rules donot indicate whether the first set of values results in a prohibition ornot. In some embodiments, the set of rules indicate that the first setof values exist and are optionally treated differently than the secondset of values. In some embodiments, the first rule defines a second setof values that are not prohibited from driving. In some embodiments, theset of rules do not indicate whether the second set of values results ina prohibition or not. In some embodiments, the set of rules indicatethat the second set of values exist and are optionally treateddifferently than the first set of values.

In some embodiments, determining, using the set of rules, the one ormore first portions of the identifier of the vehicle that are relevantto the driving restriction includes determining that the first ruledefines the first and second sets of values for the first respectiveportion of the identifier, such as step 1064 in FIG. 10M (e.g., if theset of rules includes a rule that defines two sets of valid values(optionally indicating that the two sets of values are treateddifferently) for a respective digit of a license plate, then the devicedetermines that the respective digit of the license plate is relevant tothe driving restriction). For example, because two sets of potentialvalues exist for a respective digit of a license plate, and the twovalues are treated different, then the value of the respective digit isinformative of whether the respective license plate is prohibited or notprohibited (e.g., the respective digit dictates the result or is afactor in determining the result).

The above-described manner of determining relevant portions of anidentifier (e.g., by determining whether a set of rules defines two setsof values for a respective portion of the identifier that are treateddifferently) provides a quick and efficient way of determining therelevant portions of an identifier from a set of driving restrictionrules (e.g., by analyzing whether the rules create different groups ofvalues), which simplifies the interaction between the user and theelectronic device and enhances the operability of the electronic deviceand makes the user-device interface more efficient, which additionallyreduces power usage and improves battery life of the electronic deviceby enabling the user to use the electronic device more quickly andefficiency while reducing errors in the usage of the device.

In some embodiments, receiving the set of rules associated with thedriving restriction for a geographic area includes receiving the set ofrules from a rules validation server, such as signed simplified ruleset1085 and 1079 in FIG. 10O (e.g., the set of rules is validated (e.g., bya rules validation server) to determine whether the set of rules aregenuine or whether the set of rules potentially violate the privacy ofthe user).

In some embodiments, if the validation server validates the set ofrules, then the validation server generates a set of rules to providethe electronic device (e.g., either by transmitting the set of rulesdirectly to the electronic device or transmitting the set of rules to anavigation server, which then transmits the set of rules to theelectronic device). In some embodiments, the set of rules generated bythe validation server is a signed (e.g., certified and/or encrypted)version of the original set of rules (e.g., the set of rules from therules server). In some embodiments, the set of rules generated by thevalidation server is a simplified set of rules based on the original setof rules.

In some embodiments, the set of rules is generated from a full set ofrules associated with the driving restriction for the geographic area,such as full driving restriction ruleset 1089 in FIG. 10O (e.g., thevalidation server receives the full set of rules from a rules server orany suitable rules repository) and indicates the one or more portions ofthe identifier of the vehicle that are relevant to the drivingrestriction and the valid sets of values for the one or more portions ofthe identifier of the vehicle without indicating whether the identifierof the vehicle is or it not restricted by the driving restriction (e.g.,the set of values defines the relevant portions of the license plate andthe sets of values for the respective relevant portions).

In some embodiments, the full set of rules defines the criteria in whicha vehicle is prohibited from driving in a restricted region. Forexample, the full set of rules can indicate that if the last digit of alicense plate is even, then the vehicle is prohibited from driving inthe restricted region, and if the last digit of the license plate isodd, then the vehicle is not prohibited from driving in the restrictedregion. In some embodiments, the validation server determines, based onthe full set of rules, the digits of the license plate that are relevantto the driving restriction and the digits of the license plate that arenot relevant to the driving restriction.

In some embodiments, the validation server, based on the full set ofrules, determines a first set of values for a respective relevant digitof the license plate that are prohibited from driving in the restrictedregion and a second set of values for the respective relevant digit ofthe license plate that are not prohibited from driving in the restrictedregion. For example, if the full set of rules can indicate that if thelast digit of a license plate is even, then the vehicle is prohibitedfrom driving in the restricted region, and if the last digit of thelicense plate is odd, then the vehicle is not prohibited from driving inthe restricted region, then the validation server generates a first setof values that includes even values and a second set of values thatincludes odd values. Thus, the first set of values (e.g., even values)include the values that are prohibited from driving, whereas the secondset of values (e.g., odd values) include the values that are notprohibited from driving. In some embodiments, the set of values includeonly values that are valid for the respective digit of the licenseplate. For example, if the last digit of a license plate can only benumbers and not letters, the sets of values only include numbers anddoes not include letters. In some embodiments, after determining thesets of values, the validation server generates a simplified set ofrules based on the full set of rules. In some embodiments, thesimplified set of rules indicates which digits of a license plate arerelevant (e.g., the last digit in the example provided above), and thesets of values determined above. In some embodiments, the simplified setof rules do not indicate whether a respective set of values are ofvalues that are prohibited or are of values that are not prohibited(e.g., the simplified rules define the groups, but not whether thegroups are or are not prohibited). In some embodiments, the simplifiedset of rules do indicate whether a respective set of values are ofvalues that are prohibited or are of values that are not prohibited. Insome embodiments, the simplified set of rules are generated only afterthe validation server has determined that the full set of rules do notviolate a set of privacy criteria, as will be described in furtherdetail below. In some embodiments, the validation server digitally signsthe simplified set of rules (e.g., optionally with a private keyassociated with the validation server) to authenticate that thesimplified set of rules originated from the validation server. In someembodiments, the signed and/or encrypted simplified set of rules arethen provided to the electronic device (e.g., optionally via thenavigation server).

The above-described manner of receiving a simplified set of rules (e.g.,from a rules validation server, which validates the rules and generatesthe simplified set of rules from a full set of rules) provides a quickand efficient way of distilling the rules into a set that is easilyconsumable by an electronic device (e.g., by compiling together only theinformation required to anonymize a license plate), which simplifies theinteraction between the user and the electronic device and enhances theoperability of the electronic device and makes the user-device interfacemore efficient (e.g., by pre-compiling the simplified set of rules fromthe full set of rules and providing the simplified set of rules toclient devices, without requiring each client device to process the fullset of rules), which additionally reduces power usage and improvesbattery life of the electronic device by enabling the user to use theelectronic device more quickly and efficiency while reducing errors inthe usage of the device.

In some embodiments, the rules validation server determines whether thefull set of rules satisfies one or more criteria, such as step 1094 inFIG. 10N (e.g., the validation server determines whether the full set ofrules risks violating the privacy of a user).

For example, the full set of rules indicates that every digit isrelevant, then the criteria is optionally not satisfied becauseselecting from a small set of values for every digit potentially doesnot anonymize the user's license plate enough. In another example, ifthe full set of rules results in sets of valid values for a thresholdnumber of digits with less than threshold number of values (e.g., 60%,75%, 80%, 90% of the digits have sets of value values with less than 2,3, 4, etc. valid values), than the criteria is optionally not satisfied.In some embodiments, the full set of rules satisfies the one or morecriteria if there is no risk that the set of rules would violate theuser's privacy. In some embodiments, the rules validation serverdetermines whether the full set of rules is not genuine (e.g., if thefull set of rules have an incorrect format, if the full set of rules arenot authentically signed by the rules repository or rules server). Thus,in some embodiments, the full set of rules satisfies the one or morecriteria if there is no indication that the full set of rules are notgenuine.

In some embodiments, in accordance with a determination that the fullset of rules satisfies the one or more criteria, the rules validationserver signs the generated set of rules to be transmitted to theelectronic device, such as step 1095 in FIG. 10N (e.g., the rulesvalidation server digitally signs and/or encrypts the simplified set ofrules optionally using the private key of the rules validation server),wherein the electronic device is able to decrypt the generated set ofrules (e.g., the client device has access to a public key of the rulesvalidation server and is able to decrypt the simplified set of rulesusing the public key of the rules validation server).

In some embodiments, successfully decrypting the simplified set of rulesindicates that the simplified set of rules are authentic. In someembodiments, the decryption process can include multiple communicationtransactions (e.g., including generation and/or transmission of atemporary session key, etc.). In some embodiments, the signed simplifiedset of rules is provided directly to the client electronic device. Insome embodiments, the signed simplified set of rules is provided to thenavigation server (which optionally then provides the signed simplifiedrules to the client device).

In some embodiments, in accordance with a determination that the fullset of rules does not satisfy the one or more criteria, the rulesvalidation server forgoes signing the generated set of rules, such asstep 1099 in FIG. 10N (e.g., if the full set of rules do not satisfy theone or more criteria, the full set of rules are not validated and arerejected by the rules validation server).

In some embodiments, the rules validation server does not generate thesimplified set of rules. In some embodiments, the rules validationserver discards the simplified set of rules without signing, encrypting,or otherwise transmitting the simplified set of rules to a clientdevice. In some embodiments, performing validation of the rules andsigning the validated rules ensures that the rules provided to andreceived by the client device are authentic and do not violate anyvalidation criteria. This process optionally also ensures that the ruleshave not been maliciously altered along the way. In some embodiments,the above-described validation method is performed on a client device(e.g., additionally or alternatively to validation by the rulesvalidation server) in response to receiving a set of rules (e.g., fullset of rules or simplified set of rules).

The above-described manner of generating a simplified set of rules(e.g., by determining whether the full set of rules violates orsatisfies certain criteria, then generating and signing a set ofsimplified rules based on the full set of rules) provides a quick andefficient way of validating the driving restriction rules, whichsimplifies the interaction between the user and the electronic deviceand enhances the operability of the electronic device and makes theuser-device interface more efficient (e.g., by automatically determiningwhether the rules should be provided to client devices and thusprotecting client devices from potentially malicious rules, withoutrequiring each client device to separately determine whether the rulesviolate certain criteria), which additionally reduces power usage andimproves battery life of the electronic device by enabling the user touse the electronic device more quickly and efficiency while reducingerrors in the usage of the device.

In some embodiments, after transmitting the anonymized identifier to therouting server, the electronic device receives, from the routing server,one or more suggested routes based on the anonymized identifier, such assuggested routes 1075 in FIG. 10O (e.g., the anonymized license plate isprovided to a routing server or navigation server that determines one ormore navigation routes).

In some embodiments, the routing or navigation server has access to thefull driving restriction ruleset and determines, based on the anonymizedlicense plate, whether the user's vehicle is prohibited or notprohibited from driving in a restricted region. Based on thisdetermination, the routing server optionally determines the routes thatavoid the restricted region (e.g., if the anonymized license plateindicates that the user's vehicle is prohibited) and provides thoseroutes to the electronic device. In some embodiments, the routing serverdetermines routes that do not avoid the restriction and provides thoseroutes to the electronic device, optionally with an indication that theuser's vehicle may be prohibited from driving along the route. In someembodiments, the routing server optionally determines that user'svehicle is not prohibited from driving in the restricted region (e.g.,if the anonymized license plate indicates that the user's vehicle is notprohibited) and provides, to the device, one or more routes that areselected without regard to the restricted region (e.g., is not expresslyselected to avoid the restricted region). In some embodiments, if theuser's license plate is prohibited from driving in the restrictedregion, the above-described anonymization process is performed multipletimes to generate a first license plate that is prohibited from drivingin the restricted region to receive navigation routes that avoid therestricted region, and a second license plate that is not prohibitedfrom driving in the restricted region to receive navigation routes thatare selected without regard to the restricted region. In someembodiments, the electronic device displays both routes that avoid arestricted region and routes that do not avoid the restricted region,similar to the process described above in method 700.

The above-described manner of generating navigation routes (e.g., byanonymizing the user's license plate and providing the anonymizedlicense plate to a routing server to generate navigation routes)provides a quick and efficient way of generating navigation routes,which simplifies the interaction between the user and the electronicdevice and enhances the operability of the electronic device and makesthe user-device interface more efficient (e.g., by protecting the user'sprivacy by automatically anonymizing the user's license plate whenrequesting navigation routes, without requiring the user to manuallyanonymize the vehicle's license plate before transmission to the routingserver), which additionally reduces power usage and improves batterylife of the electronic device by enabling the user to use the electronicdevice more quickly and efficiency while reducing errors in the usage ofthe device.

It should be understood that the particular order in which theoperations in FIG. 11 have been described is merely exemplary and is notintended to indicate that the described order is the only order in whichthe operations could be performed. One of ordinary skill in the artwould recognize various ways to reorder the operations described herein.Additionally, it should be noted that details of other processesdescribed herein with respect to other methods described herein (e.g.,methods 700 and 900) are also applicable in an analogous manner tomethod 1100 described above with respect to FIG. 11 . For example, theoperation of the electronic device anonymizing a vehicle identifierdescribed above with reference to method 1100 optionally has one or moreof the characteristics of displaying customized navigation routes,receiving information about characteristics of respective vehicles,etc., described herein with reference to other methods described herein(e.g., methods 700 and 900). For brevity, these details are not repeatedhere.

The operations in the information processing methods described aboveare, optionally, implemented by running one or more functional modulesin an information processing apparatus such as general purposeprocessors (e.g., as described with respect to FIGS. 1A-1B, 3, 5A-5B) orapplication specific chips. Further, the operations described above withreference to FIG. 11 are, optionally, implemented by components depictedin FIGS. 1A-1B. For example, receiving operation 1102, determiningoperation 1104, generating operation 1110, and transmitting operation1116 are, optionally, implemented by event sorter 170, event recognizer180, and event handler 190. Event monitor 171 in event sorter 170detects a contact on touch-sensitive surface 504, and event dispatchermodule 174 delivers the event information to application 136-1. Arespective event recognizer 180 of application 136-1 compares the eventinformation to respective event definitions 186, and determines whethera first contact at a first location on the touch-sensitive surfacecorresponds to a predefined event or sub-event, such as selection of anobject on a user interface. When a respective predefined event orsub-event is detected, event recognizer 180 activates an event handler190 associated with the detection of the event or sub-event. Eventhandler 190 optionally utilizes or calls data updater 176 or objectupdater 177 to update the application internal state 192. In someembodiments, event handler 190 accesses a respective GUI updater 178 toupdate what is displayed by the application. Similarly, it would beclear to a person having ordinary skill in the art how other processescan be implemented based on the components depicted in FIGS. 1A-1B.

As described above, one aspect of the present technology is thegathering and use of data available from specific and legitimate sourcesto improve the display of device location information to users. Thepresent disclosure contemplates that in some instances, this gathereddata may include personal information data that uniquely identifies orcan be used to identify a specific person. Such personal informationdata can include demographic data, location-based data, onlineidentifiers, telephone numbers, email addresses, home addresses, data orrecords relating to a user's health or level of fitness (e.g., vitalsigns measurements, medication information, exercise information), dateof birth, license plate numbers, or any other personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used todisplay the user's current location, display the user's favorite orrecently visited locations, and/or provide suggested navigation routes.Accordingly, use of such personal information data enables users to havemore information about the user's or the device's location. Further,other uses for personal information data that benefit the user are alsocontemplated by the present disclosure.

The present disclosure contemplates that those entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities would beexpected to implement and consistently apply privacy practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. Such informationregarding the use of personal data should be prominent and easilyaccessible by users, and should be updated as the collection and/or useof data changes. Personal information from users should be collected forlegitimate uses only. Further, such collection/sharing should occur onlyafter receiving the consent of the users or other legitimate basisspecified in applicable law. Additionally, such entities should considertaking any needed steps for safeguarding and securing access to suchpersonal information data and ensuring that others with access to thepersonal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations that may serve to imposea higher standard. For instance, in the US, collection of or access tocertain health data may be governed by federal and/or state laws, suchas the Health Insurance Portability and Accountability Act (HIPAA);whereas health data in other countries may be subject to otherregulations and policies and should be handled accordingly.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, the presenttechnology can be configured to allow users to select to “opt in” or“opt out” of participation in the collection of personal informationdata during registration for services or anytime thereafter. In anotherexample, users can select not to enable customized navigation routes. Inyet another example, users can select to limit the sharing of thedevice's location information or entirely block the display ofcustomized routes or license plate information. In addition to providing“opt in” and “opt out” options, the present disclosure contemplatesproviding notifications relating to the access or use of personalinformation. For instance, a user may be notified upon displaying themap application that the characteristics of their vehicle (e.g., licenseplate number) will be used and then reminded again before customizedroutes are determined and/or displayed.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing identifiers, controlling the amount orspecificity of data stored (e.g., collecting location data at city levelrather than at an address level), controlling how data is stored (e.g.,aggregating data across users), and/or other methods such asdifferential privacy.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, locationinformation can be generated and delivered to users based onnon-specific information data or a bare minimum amount of identifyinginformation, such as the determination of suggested routes based on theaverage driving range of vehicles similar to the user's vehicles.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users,such as by anonymizing a vehicle's license plate as described above withrespect to method 1100.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

The invention claimed is:
 1. A method, comprising: at an electronicdevice in communication with a display generation component and one ormore input devices: displaying, via the display generation component, amap user interface; while displaying the map user interface, receiving,via the one or more input devices, a first user input corresponding to arequest to display directions from a first location to a second locationvia a given mode of transportation; and in response to receiving thefirst user input: in accordance with a determination that a firstvehicle is a currently selected vehicle for which to display directionsin the map user interface, displaying, in the map user interface, afirst suggested route from the first location to the second locationbased on a first characteristic of the first vehicle; and in accordancewith a determination that a second vehicle, different from the firstvehicle, is the currently selected vehicle for which to displaydirections in the map user interface, displaying, in the map userinterface, a second suggested route from the first location to thesecond location, different from the first suggested route, based on asecond characteristic of the second vehicle; while navigating along thefirst suggested route, determining that the device has arrived at asuggested stop for increasing a remaining driving range of the firstvehicle; and in response to determining that the device has arrived atthe suggested stop for increasing the remaining driving range of thefirst vehicle: in accordance with a determination that an accessory of afirst type is required to increase the remaining driving range of thefirst vehicle, displaying, via the display generation component, anindication of the accessory of the first type.
 2. The method of claim 1,wherein: the first characteristic of the first vehicle includes a firstcurrent estimated driving range for the first vehicle; the firstsuggested route is based on the first current estimated driving range;the second characteristic of the second vehicle includes a secondcurrent estimated driving range for the second vehicle, different fromthe first current estimated driving range; and the second suggestedroute is based on the second current estimated driving range.
 3. Themethod of claim 2, wherein: in accordance with a determination that thefirst current estimated driving range is less than a driving distance ofthe first suggested route from the first location to the secondlocation, the first suggested route includes a suggested stop forincreasing a remaining driving range of the first vehicle.
 4. The methodof claim 3, wherein: in accordance with a determination that the firstvehicle is associated with a first charging network, the suggested stopfor increasing the remaining driving range of the first vehicle is afirst stop associated with the first charging network.
 5. The method ofclaim 1, wherein: the first characteristic of the first vehicle includesa first current estimated driving range for the first vehicle; and thefirst suggested route is based on the first current estimated drivingrange, the method further comprising: in response to the first userinput: in accordance with a determination that a third vehicle iscurrently selected for which to display directions in the map userinterface, displaying, in the map user interface, a third suggestedroute from the first location to the second location, that is not basedon a current estimated driving range for a vehicle.
 6. The method ofclaim 1, wherein: displaying the first suggested route from the firstlocation to the second location includes displaying an estimated totaltravel time for the first suggested route; and in accordance with adetermination that the first suggested route includes a suggested stopfor increasing a remaining driving range of the first vehicle, theestimated total travel time includes an estimated time to increase theremaining driving range of the first vehicle at the suggested stop. 7.The method of claim 1, further comprising: displaying, via the displaygeneration component, one or more representations of one or moresegments associated with the first suggested route, wherein a respectiverepresentation of a respective segment includes an indication of anestimated state of the first characteristic of the first vehicle duringthe respective segment.
 8. The method of claim 1, further comprising:while the first vehicle is the currently selected vehicle and whiledisplaying the first suggested route from the first location to thesecond location, receiving, via the one or more input devices, a userinput corresponding to a request to select the second vehicle as thecurrently selected vehicle; and in response to receiving the user inputcorresponding to the request to select the second vehicle as thecurrently selected vehicle, displaying, in the map user interface, thesecond suggested route.
 9. The method of claim 1, further comprising:while navigating along the first suggested route, determining that thedevice has arrived at a suggested stop for increasing a remainingdriving range for the first vehicle; in response to determining that thedevice has arrived at the suggested stop for increasing an effectiverange of the first vehicle, displaying, via the display generationcomponent, a first affordance to pause the navigation along the firstsuggested route; while displaying the first affordance to pause thenavigation, receiving, via the one or more input devices, a user inputselecting the first affordance; and in response to receiving the userinput selecting the first affordance, displaying, via the displaygeneration component: a second affordance to resume navigating along thefirst suggested route; and an indication of the first characteristic ofthe first vehicle while it is increasing.
 10. The method of claim 1,further comprising: while navigating along the first suggested route,determining that a current estimated driving range for the first vehicleis less than a remaining driving distance of the first suggested routefrom a current location to the second location; and in response todetermining that the current estimated driving range for the firstvehicle is less than the remaining driving distance of the firstsuggested route from the current location to the second location,updating the first suggested route to include a suggested stop forincreasing a remaining driving range of the first vehicle.
 11. Themethod of claim 1, wherein: the first characteristic of the firstvehicle is associated with a first driving restriction for the firstvehicle; the first suggested route is based on the first drivingrestriction; the second characteristic of the second vehicle isassociated with a second driving restriction for the second vehicle,different from the first driving restriction; and the second suggestedroute is based on the second driving restriction.
 12. The method ofclaim 11, wherein: the first driving restriction is determined using ananonymized characteristic corresponding to the first characteristic ofthe first vehicle.
 13. The method of claim 1, wherein: the firstcharacteristic of the first vehicle is associated with a first drivingrestriction for the first vehicle; and the first suggested route isbased on the first driving restriction, the method further comprising:in response to the first user input: in accordance with a determinationthat no vehicle is currently selected for which to display directions inthe map user interface, displaying, in the map user interface, a thirdsuggested route from the first location to the second location, that isnot based on a driving restriction.
 14. The method of claim 13, wherein:in accordance with a determination that the third suggested route passesthrough an area restricted by a respective driving restriction,displaying, via the display generation component, an indication that thethird suggested route passes through the area restricted by a drivingrestriction.
 15. The method of claim 1, further comprising: inaccordance with a determination that a given route from the firstlocation to the second location is associated with a drivingrestriction: in accordance with a determination that one or morecriteria are satisfied, displaying, via the display generationcomponent, an affordance for adding information about a respectivevehicle to the map user interface; receiving, via the one or more inputdevices, a user input selecting the affordance; and in response toreceiving the user input, initiating a process to add the informationabout the respective vehicle to the map user interface.
 16. The methodof claim 1, further comprising: while navigating along the firstsuggested route, determining that a current location of the devicesatisfies one or more criteria associated with a driving restriction ofthe first suggested route; and in response to determining that thecurrent location satisfies the one or more criteria associated with thedriving restriction, displaying, via the display generation component,an indication of the driving restriction.
 17. An electronic device,comprising: one or more processors; memory; and one or more programs,wherein the one or more programs are stored in the memory and configuredto be executed by the one or more processors, the one or more programsincluding instructions for: displaying, via a display generationcomponent, a map user interface; while displaying the map userinterface, receiving, via one or more input devices, a first user inputcorresponding to a request to display directions from a first locationto a second location via a given mode of transportation; and in responseto receiving the first user input: in accordance with a determinationthat a first vehicle is a currently selected vehicle for which todisplay directions in the map user interface, displaying, in the mapuser interface, a first suggested route from the first location to thesecond location based on a first characteristic of the first vehicle;and in accordance with a determination that a second vehicle, differentfrom the first vehicle, is the currently selected vehicle for which todisplay directions in the map user interface, displaying, in the mapuser interface, a second suggested route from the first location to thesecond location, different from the first suggested route, based on asecond characteristic of the second vehicle; while navigating along thefirst suggested route, determining that the device has arrived at asuggested stop for increasing a remaining driving range of the firstvehicle; and in response to determining that the device has arrived atthe suggested stop for increasing the remaining driving range of thefirst vehicle: in accordance with a determination that an accessory of afirst type is required to increase the remaining driving range of thefirst vehicle, displaying, via the display generation component, anindication of the accessory of the first type.
 18. A non-transitorycomputer readable storage medium storing one or more programs, the oneor more programs comprising instructions, which when executed by one ormore processors of an electronic device, cause the electronic device toperform a method comprising: displaying, via a display generationcomponent, a map user interface; while displaying the map userinterface, receiving, via one or more input devices, a first user inputcorresponding to a request to display directions from a first locationto a second location via a given mode of transportation; and in responseto receiving the first user input: in accordance with a determinationthat a first vehicle is a currently selected vehicle for which todisplay directions in the map user interface, displaying, in the mapuser interface, a first suggested route from the first location to thesecond location based on a first characteristic of the first vehicle;and in accordance with a determination that a second vehicle, differentfrom the first vehicle, is the currently selected vehicle for which todisplay directions in the map user interface, displaying, in the mapuser interface, a second suggested route from the first location to thesecond location, different from the first suggested route, based on asecond characteristic of the second vehicle; while navigating along thefirst suggested route, determining that the device has arrived at asuggested stop for increasing a remaining driving range of the firstvehicle; and in response to determining that the device has arrived atthe suggested stop for increasing the remaining driving range of thefirst vehicle: in accordance with a determination that an accessory of afirst type is required to increase the remaining driving range of thefirst vehicle, displaying, via the display generation component, anindication of the accessory of the first type.
 19. The electronic deviceof claim 17, wherein: the first characteristic of the first vehicleincludes a first current estimated driving range for the first vehicle;the first suggested route is based on the first current estimateddriving range; the second characteristic of the second vehicle includesa second current estimated driving range for the second vehicle,different from the first current estimated driving range; and the secondsuggested route is based on the second current estimated driving range.20. The electronic device of claim 19, wherein: in accordance with adetermination that the first current estimated driving range is lessthan a driving distance of the first suggested route from the firstlocation to the second location, the first suggested route includes asuggested stop for increasing a remaining driving range of the firstvehicle.
 21. The electronic device of claim 20, wherein: in accordancewith a determination that the first vehicle is associated with a firstcharging network, the suggested stop for increasing the remainingdriving range of the first vehicle is a first stop associated with thefirst charging network.
 22. The electronic device of claim 17, wherein:the first characteristic of the first vehicle includes a first currentestimated driving range for the first vehicle; and the first suggestedroute is based on the first current estimated driving range, theinstructions further for: in response to the first user input: inaccordance with a determination that a third vehicle is currentlyselected for which to display directions in the map user interface,displaying, in the map user interface, a third suggested route from thefirst location to the second location, that is not based on a currentestimated driving range for a vehicle.
 23. The electronic device ofclaim 17, wherein: displaying the first suggested route from the firstlocation to the second location includes displaying an estimated totaltravel time for the first suggested route; and in accordance with adetermination that the first suggested route includes a suggested stopfor increasing a remaining driving range of the first vehicle, theestimated total travel time includes an estimated time to increase theremaining driving range of the first vehicle at the suggested stop. 24.The electronic device of claim 17, the instructions for: displaying, viathe display generation component, one or more representations of one ormore segments associated with the first suggested route, wherein arespective representation of a respective segment includes an indicationof an estimated state of the first characteristic of the first vehicleduring the respective segment.
 25. The electronic device of claim 17,the instructions for: while the first vehicle is the currently selectedvehicle and while displaying the first suggested route from the firstlocation to the second location, receiving, via the one or more inputdevices, a user input corresponding to a request to select the secondvehicle as the currently selected vehicle; and in response to receivingthe user input corresponding to the request to select the second vehicleas the currently selected vehicle, displaying, in the map userinterface, the second suggested route.
 26. The electronic device ofclaim 17, the instructions for: while navigating along the firstsuggested route, determining that the device has arrived at a suggestedstop for increasing a remaining driving range for the first vehicle; inresponse to determining that the device has arrived at the suggestedstop for increasing an effective range of the first vehicle, displaying,via the display generation component, a first affordance to pause thenavigation along the first suggested route; while displaying the firstaffordance to pause the navigation, receiving, via the one or more inputdevices, a user input selecting the first affordance; and in response toreceiving the user input selecting the first affordance, displaying, viathe display generation component: a second affordance to resumenavigating along the first suggested route; and an indication of thefirst characteristic of the first vehicle while it is increasing. 27.The electronic device of claim 17, the instructions for: whilenavigating along the first suggested route, determining that a currentestimated driving range for the first vehicle is less than a remainingdriving distance of the first suggested route from a current location tothe second location; and in response to determining that the currentestimated driving range for the first vehicle is less than the remainingdriving distance of the first suggested route from the current locationto the second location, updating the first suggested route to include asuggested stop for increasing a remaining driving range of the firstvehicle.
 28. The electronic device of claim 17, wherein: the firstcharacteristic of the first vehicle is associated with a first drivingrestriction for the first vehicle; the first suggested route is based onthe first driving restriction; the second characteristic of the secondvehicle is associated with a second driving restriction for the secondvehicle, different from the first driving restriction; and the secondsuggested route is based on the second driving restriction.
 29. Theelectronic device of claim 28, wherein: the first driving restriction isdetermined using an anonymized characteristic corresponding to the firstcharacteristic of the first vehicle.
 30. The electronic device of claim17, wherein: the first characteristic of the first vehicle is associatedwith a first driving restriction for the first vehicle; and the firstsuggested route is based on the first driving restriction, theinstructions further for: in response to the first user input: inaccordance with a determination that no vehicle is currently selectedfor which to display directions in the map user interface, displaying,in the map user interface, a third suggested route from the firstlocation to the second location, that is not based on a drivingrestriction.
 31. The electronic device of claim 30, wherein: inaccordance with a determination that the third suggested route passesthrough an area restricted by a respective driving restriction,displaying, via the display generation component, an indication that thethird suggested route passes through the area restricted by a drivingrestriction.
 32. The electronic device of claim 17, the instructionsfor: in accordance with a determination that a given route from thefirst location to the second location is associated with a drivingrestriction: in accordance with a determination that one or morecriteria are satisfied, displaying, via the display generationcomponent, an affordance for adding information about a respectivevehicle to the map user interface; receiving, via the one or more inputdevices, a user input selecting the affordance; and in response toreceiving the user input, initiating a process to add the informationabout the respective vehicle to the map user interface.
 33. Theelectronic device of claim 17, the instructions for: while navigatingalong the first suggested route, determining that a current location ofthe device satisfies one or more criteria associated with a drivingrestriction of the first suggested route; and in response to determiningthat the current location satisfies the one or more criteria associatedwith the driving restriction, displaying, via the display generationcomponent, an indication of the driving restriction.
 34. Thenon-transitory computer readable storage medium of claim 18, wherein:the first characteristic of the first vehicle includes a first currentestimated driving range for the first vehicle; the first suggested routeis based on the first current estimated driving range; the secondcharacteristic of the second vehicle includes a second current estimateddriving range for the second vehicle, different from the first currentestimated driving range; and the second suggested route is based on thesecond current estimated driving range.
 35. The non-transitory computerreadable storage medium of claim 34, wherein: in accordance with adetermination that the first current estimated driving range is lessthan a driving distance of the first suggested route from the firstlocation to the second location, the first suggested route includes asuggested stop for increasing a remaining driving range of the firstvehicle.
 36. The non-transitory computer readable storage medium ofclaim 35, wherein: in accordance with a determination that the firstvehicle is associated with a first charging network, the suggested stopfor increasing the remaining driving range of the first vehicle is afirst stop associated with the first charging network.
 37. Thenon-transitory computer readable storage medium of claim 18, wherein:the first characteristic of the first vehicle includes a first currentestimated driving range for the first vehicle; and the first suggestedroute is based on the first current estimated driving range, the methodfurther comprising: in response to the first user input: in accordancewith a determination that a third vehicle is currently selected forwhich to display directions in the map user interface, displaying, inthe map user interface, a third suggested route from the first locationto the second location, that is not based on a current estimated drivingrange for a vehicle.
 38. The non-transitory computer readable storagemedium of claim 18, wherein: displaying the first suggested route fromthe first location to the second location includes displaying anestimated total travel time for the first suggested route; and inaccordance with a determination that the first suggested route includesa suggested stop for increasing a remaining driving range of the firstvehicle, the estimated total travel time includes an estimated time toincrease the remaining driving range of the first vehicle at thesuggested stop.
 39. The non-transitory computer readable storage mediumof claim 18, the method further comprising: displaying, via the displaygeneration component, one or more representations of one or moresegments associated with the first suggested route, wherein a respectiverepresentation of a respective segment includes an indication of anestimated state of the first characteristic of the first vehicle duringthe respective segment.
 40. The non-transitory computer readable storagemedium of claim 18, the method further comprising: while the firstvehicle is the currently selected vehicle and while displaying the firstsuggested route from the first location to the second location,receiving, via the one or more input devices, a user input correspondingto a request to select the second vehicle as the currently selectedvehicle; and in response to receiving the user input corresponding tothe request to select the second vehicle as the currently selectedvehicle, displaying, in the map user interface, the second suggestedroute.
 41. The non-transitory computer readable storage medium of claim18, the method further comprising: while navigating along the firstsuggested route, determining that the device has arrived at a suggestedstop for increasing a remaining driving range for the first vehicle; inresponse to determining that the device has arrived at the suggestedstop for increasing an effective range of the first vehicle, displaying,via the display generation component, a first affordance to pause thenavigation along the first suggested route; while displaying the firstaffordance to pause the navigation, receiving, via the one or more inputdevices, a user input selecting the first affordance; and in response toreceiving the user input selecting the first affordance, displaying, viathe display generation component: a second affordance to resumenavigating along the first suggested route; and an indication of thefirst characteristic of the first vehicle while it is increasing. 42.The non-transitory computer readable storage medium of claim 18, themethod further comprising: while navigating along the first suggestedroute, determining that a current estimated driving range for the firstvehicle is less than a remaining driving distance of the first suggestedroute from a current location to the second location; and in response todetermining that the current estimated driving range for the firstvehicle is less than the remaining driving distance of the firstsuggested route from the current location to the second location,updating the first suggested route to include a suggested stop forincreasing a remaining driving range of the first vehicle.
 43. Thenon-transitory computer readable storage medium of claim 18, wherein:the first characteristic of the first vehicle is associated with a firstdriving restriction for the first vehicle; the first suggested route isbased on the first driving restriction; the second characteristic of thesecond vehicle is associated with a second driving restriction for thesecond vehicle, different from the first driving restriction; and thesecond suggested route is based on the second driving restriction. 44.The non-transitory computer readable storage medium of claim 43,wherein: the first driving restriction is determined using an anonymizedcharacteristic corresponding to the first characteristic of the firstvehicle.
 45. The non-transitory computer readable storage medium ofclaim 18, wherein: the first characteristic of the first vehicle isassociated with a first driving restriction for the first vehicle; andthe first suggested route is based on the first driving restriction, themethod further comprising: in response to the first user input: inaccordance with a determination that no vehicle is currently selectedfor which to display directions in the map user interface, displaying,in the map user interface, a third suggested route from the firstlocation to the second location, that is not based on a drivingrestriction.
 46. The non-transitory computer readable storage medium ofclaim 45, wherein: in accordance with a determination that the thirdsuggested route passes through an area restricted by a respectivedriving restriction, displaying, via the display generation component,an indication that the third suggested route passes through the arearestricted by a driving restriction.
 47. The non-transitory computerreadable storage medium of claim 18, the method further comprising: inaccordance with a determination that a given route from the firstlocation to the second location is associated with a drivingrestriction: in accordance with a determination that one or morecriteria are satisfied, displaying, via the display generationcomponent, an affordance for adding information about a respectivevehicle to the map user interface; receiving, via the one or more inputdevices, a user input selecting the affordance; and in response toreceiving the user input, initiating a process to add the informationabout the respective vehicle to the map user interface.
 48. Thenon-transitory computer readable storage medium of claim 18, the methodfurther comprising: while navigating along the first suggested route,determining that a current location of the device satisfies one or morecriteria associated with a driving restriction of the first suggestedroute; and in response to determining that the current locationsatisfies the one or more criteria associated with the drivingrestriction, displaying, via the display generation component, anindication of the driving restriction.
 49. The method of claim 1,further comprising: in response to determining that the device hasarrived at the suggested stop for increasing the remaining driving rangeof the first vehicle: in accordance with a determination that anaccessory of a second type, different from the first type, is requiredto increase the remaining driving range of the first vehicle,displaying, via the display generation component, an indication of theaccessory of the second type.
 50. The electronic device of claim 17, theinstructions further for: in response to determining that the device hasarrived at the suggested stop for increasing the remaining driving rangeof the first vehicle: in accordance with a determination that anaccessory of a second type, different from the first type, is requiredto increase the remaining driving range of the first vehicle,displaying, via the display generation component, an indication of theaccessory of the second type.
 51. The non-transitory computer readablestorage medium of claim 18, the method further comprising: in responseto determining that the device has arrived at the suggested stop forincreasing the remaining driving range of the first vehicle: inaccordance with a determination that an accessory of a second type,different from the first type, is required to increase the remainingdriving range of the first vehicle, displaying, via the displaygeneration component, an indication of the accessory of the second type.